4 ms·
Are we talking about Wayland or X11 here? Because like the article mentioned, Wayland is now 15 years old and still sucks. Sure sounds like the Wayland design i
by okasaki 2y ago
Are we talking about Wayland or X11 here? Because like the article mentioned, Wayland is now 15 years old and still sucks. Sure sounds like the Wayland design is untenable.
- orangeboats 2y ago> 15 years old and still sucks People dragged their feet on Wayland support for at least 10 years.
- okasaki 2y agoYes, because it sucks.
- orangeboats 2y agoMaybe because no one bothered to improve it for over a decade? ;) The Wayland developers have limited manpower. Obviously it would take a long them for them to get Wayland to reach a critical mass when there wasn't support from the community. Sort of feels like a self-fulfilling prophecy.
- ahartmetz 2y agoThe real problem was that Wayland was extremely bare-bones initially and needed many extensions to approach the usefulness of X11 for desktop use - it basically just supported dispatching input and blitting rectangles. And initially, getting extensions standardized was like pulling teeth. These days, "obvious" extensions get in in a matter of months (about one DE release cycle), not to mention that most already exist by now.
- The_Colonel 2y agoWhat's stopping you from using (and even developing) X11? It's an open competition. Wayland might reach feature parity in 2, 5, 10, or 20 years, and I'm fine waiting, because while X11 can kinda work well now, its archaic design with 10 levels of hacks will likely make it extremely hard to support new needs (it already struggles with some existing use cases).