3 ms·
Wayland was started primarily by those who were maintaining X11. There is almost nobody who is both capable of working on X11 and wants to work on it. The red
by aidenn0 11mo ago
Wayland was started primarily by those who were maintaining X11. There is almost nobody who is both capable of working on X11 and wants to work on it.
The redesign also reflects their priorities. The best analogy I can come up with is imagine a small group of people maintaining an old car frame and mechanical workings. They work hard to keep the engine running, but it's in a chassis with leaf springs and direct steering. It also has lots of vestigial things like a hand-crank even though most people have been using an electric starter for years. Other people use this as a platform to make complete cars with body &c. but this is both too much and too old for the small group to maintain themselves.
So they build a new, more modern engine and wait for other people to build a car around it, which is more sustainable amount of work for them. Lots of other people complain that the engine isn't a car, and when they use the engine with one brand of car, the brakes don't work and when they use it with another brand of car, the steering doesn't work. This makes sense, since previously the underlying platform implemented much of those, but now it doesn't and everyone is figuring out how to build those and couple them to the new engine.
Eventually you reach the point where each brand has created its own brakes, suspension &c. that mostly work about the same, but the only actual common component is the engine now. That's about where we are today.
- simion314 11mo ago>Wayland was started primarily by those who were maintaining X11. There is almost nobody who is both capable of working on X11 and wants to work on it. Isn't wayland just soem protocol? so did the ex X11 devs wrote soem specifications and then soem went to GNOME< some to KDE and others are just editing the specifications ? I think the issue is that there is no wayland library that a DE can use so everyone is forced to implement it as part of the DE , so the end result is a lot of missing features and incompatibility. I could be wrong, I still run Linux but I decided years ago to stop following the Linux drama, I will use Kubuntu LTS and hopefully when it drops X11 the Wayland implementation and the X11 fallback would be usable.
- prmoustache 11mo agowlroots is one such library.
- aidenn0 11mo agoFrom the wayland readme: > The wayland protocol is essentially only about input handling and buffer management So sending input to clients and managing the buffers needed is what wayland implements. Everything else is either done in the clients (e.g. rendering) or the compositor (pretty much everything else). Note that this is a subset of what X11 did (though rendering had pretty much already moved to the client for modern applications). X11, of course, handled input, and it also provided an IPC mechanism (which is how clients e.g. communicated things to the WM). Wayland, at its core, is just those two things.
- simion314 11mo agoYeah, so is not shitty for those claimed X11 devs to drop X11 since is hard and make a spreadsheet with a specification of a subset of X11 , then let other suckers implement it and maybe some other suckers create specifications of the missifng part they refused or were incapable to create. Probably all was exactly as Red Hat planned, if it works for GNOME then the rest is ignored or if it does not work for the rest then is a bonus.