Why?
Why?
And that having fucktons of incompatible compositors because wayland, by design, does not want to standardize things they decided would be harmful to myself if I needed them is also a good path forward.
Meanwhile the very real problem of "developers can't write an application that targets wayland, is brushed under the carpet, and then the entire house it's in is also buried in sand. Devs can target gnome, kde or whatever. But they'd have to support them separately. And there are certain devs who explicitly say they will not be implementing wayland support because of these issues. But at least we have solved XEyes's security issues!
Google and Microsoft pioneered this a long time ago.
Maybe because so they can introduce it later as "new". /s
Last time I started a wayland plasma session it kept resetting my screen brightness to 100% every time they woke from sleep. The time before that I crashed the entire desktop, dropping me back to the terminal, when I tried to drag a hyperlink between windows.
Those might have been fixed and I might try wayland again next time I update and reboot.
I don't care about its supposed advantages.
Wayland reminds me very much of the Disk Utility application that shipped with Mac OS X El Capitan. The developers rewrote it because the original person who wrote it wasn't at Apple anymore and it ended up being pretty much useless due to massive amount of missing features.
>I don't care about its supposed advantages
Since it will be the only game in town soon, it's time to start caring - or people will also have to change DEs and other apps, which would be much more trouble than getting on with the program.
thankfully this hasn't been a problem so far, hopefully the end of x11 is still about 20 years away, like fusion.
Also there's no kill switch so I don't have to update. I wonder how long I can hold plasma and qt without breaking some other package.
Are there any, though ? AFAIK it has mechanisms to stop spyware programs (Chrome, Firefox, etc.) communicating with each other.