Those deliberately-missing features in Wayland would have been a good opportunity to instead provide an official API plus an official security/privacy framework. Pretending that the hard problems are out of scope was such a disappointing strategy.
It is mindblowing to me that so many people think that just ripping out functionality and completely eliminating certain legitimate usecases is "progress".
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!
> It is mindblowing to me that so many people think that just ripping out functionality and completely eliminating certain legitimate usecases is "progress".
Google and Microsoft pioneered this a long time ago.
Maybe because so they can introduce it later as "new". /s
