22 ms·
I have no worries about this. Linux distributions always do a couple of releases of "disasters", (e.g. KDE 4) before it starts becoming stable. Wayland is the
by sgt 16y ago
I have no worries about this. Linux distributions always do a couple of releases of "disasters", (e.g. KDE 4) before it starts becoming stable.
Wayland is theoretically superior and with iteration after iteration, I'm sure it's going to come out on top. Just don't be one of the early adopters, but that's a given when it comes to Ubuntu, in my experience (unless you really do like the risks involved with cutting edge software).
The truth is, X is just too old fashioned and it's like trying to spend time maintaining an old car from the 1970s instead of just buying a new car with electronic fuel injection and excellent brakes.
- sqrt17 16y agoHave you ever tried to repair things in a new car with electronic fuel injection and computer-driven brakes? A huge advantage of X11 and all that other "70s technology" is that you can fix things more easily because it's built for being maintainable in the first place. Having said that, I think that splitting the X server into one lightweight compositing manager and one slightly less heavyweight X-server-on-top-of-the-compositing-manager is less of a disaster than what we got with KDE4. I'll only start worrying when KDE and Gnome catch up and they start having UI programs talk directly to the compositing engine.
- barkingcat 16y agoI'm not sure about the easy to fix concept. By all accounts the X codebase is one nasty beast to wrap your head around. The protocols are well documented, but the actual code - it takes some crazy digging to actually understand it enough to be able to fix things in X-land.
- wmf 16y agoRealistically, something like 1% of Ubuntu users could fix their xorg.conf. Either it works or it doesn't, and in my experience a simpler architecture (Wayland) is more likely to work.