Comment by dismalaf
5 months ago
Who broke it? It works. It's still there. Plenty of distros use it still...
The maintainers just got sick of maintaining it and moved on...
5 months ago
Who broke it? It works. It's still there. Plenty of distros use it still...
The maintainers just got sick of maintaining it and moved on...
This is such a "technically true, the worst kind of true" take.
Whatever group or person "got Wayland going" collectively or individually made a clear choice to abandon a lot of load-bearing standards, and its disengenuous to not recognize that; and I think why people (like me) still complain is to note that this was at least arguably a mistake.
Wayland's rollout was long and terrible, and more cooperation (as opposed to what actually happened, which was likely "move fast and break things because advancement and shiny things since we are now much more corporate" might have been better.
"Abandoning" standards was done because X11 was the standard and it was too complicated for even the X11 maintainers to want to deal with. Wayland, for better or worse, splits up a lot of responsibilities and even offloads some to the app developer...
Linux has nothing to do with cooperation. It's a survival of the fittest scenario. People make things, then other people either adopt them or don't.
Gnome has a working screen reader on Wayland. They have APIs for accessibility on Gnome. Should RH/Gnome be responsible for all the Wayland compositors and DEs that haven't implemented it? Should they be responsible for a proprietary app that chooses not to work with what they're given?
Again, X11 exists, works, and no one is forcing it to go away. Devs can ignore Gnome/Red Hat things and do whatever they want. Or they can make their own thing work. Blaming others for not doing work they're too lazy to do is wild...