4 ms·
The big problem with Wayland is that it isn't actually an obvious improvement over X. X is awful and long in the tooth and well overdue for replacement, but the
by AnIdiotOnTheNet 7y ago
The big problem with Wayland is that it isn't actually an obvious improvement over X. X is awful and long in the tooth and well overdue for replacement, but the best I can say about Wayland is that it is just differently awful. It's been in development for what, over a decade now? And it still would be missing a lot of basic functionality if it weren't for people like Drew Devault stepping up and creating new standard protocols to cover for it, as well as a library to make dealing with all these protocols less of a nightmare.
- majewsky 7y agoI'm not sure which point you're trying to make. Of course every new technology needs someone to do the work. That doesn't take away from the technology's merit. If Drew is now doing all this work, then great! Now is the best time ever to be adopting Wayland. (Speaking as someone who just switched to Sway two weeks ago.)
- AnIdiotOnTheNet 7y agoMy point is that in setting out to replace X, they created something that doesn't actually do that and it took about ten years for third parties to do it for them and there still isn't consensus that Wayland is superior to X. In comparison, Windows Vista introduced a perfectly functional compositor with brand new driver model at about the same time and I can't think of any significant functionality it lost in the process, while I can name many significant improvements.
- mappu 7y ago> I can't think of any significant functionality it lost in the process Hardware acceleration for 2D operations (GDI)