• 0 Posts
  • 15 Comments
Joined 1 年前
cake
Cake day: 2023年6月18日

help-circle
  • I had been led to believe that one of Wayland’s strength was solving the correct window coordinates save-and-restore problem. Does someone know what happened here?

    It’s literally the opposite. Windows aren’t allowed to position themselves on Wayland (because it’s unsafe or something). Window state save restoration must implemented by the compositor itself. Not sure about GNOME, but KDE doesn’t have that.









  • I wonder if they consulted Plasma devs about it. Sure they said that they aim to make Wayland ready for Plasma 6, but it didn’t sound like it was an actual plan for 6.0. After all they got their hands full with Qt 6 porting, and there are still major roadblocks with completing Wayland support, while 6.0 is about to have its alpha release already.

    Knowing Fedora devs however, I suspect they didn’t. They switched to Plasma Wayland by default several Fedora releases ago, when it was in no way ready. I guess I will switch to a different distro when this time comes.





  • That’s how they do it. They send their “proposal” and immediately implement it in Chrome (with work on that being started long before “proposal” is made public obviously). Then they start using it on their own websites (with compatibility for now) and start propaganda campaign to push webdevs to use it too (which they do of course). Then they start complaining that other browsers’ developers are slow to implement this new “standard” (at this stage they won’t call it a “proposal” anymore) and are “stifling development of the web” or being actively malicious because they are jealous of Chrome or something. Then compatibility mode on their websites is first subtly broken so that users once again will witness how Chrome is superior browser and then removed outright. Boom, we have a new web standard!