Writing a Wayland compositor on top of wlroots is probably a larger project than writing a window manager for X. But it's not orders of magnitude, wlroots handles a whole lot of the dirty work for you.
The X protocol [...] doesn't spoil like cabbage.
It actually does. The protocol doesn't handle things we expect from modern hardware and software. And the implementation certainly rots away as the rest of the software ecosystem changes in ways which will slowly make Xorg more and more broken. Drivers will change in ways which expose Xorg bugs. GUI toolkits will introduce bugs in their X backends and introduce new features which don't work on their X backend. Nobody maintains X anymore, and something like a display server in a rapidly changing software and hardware ecosystem requires maintenance to keep functioning.
None of this is to say the Xmonad developer should spend time rewriting their project to use wlroots instead of X. But as long as it requires X, it's living om borrowed time.
Screen tearing is more or less unavoidable on X. I've had tearing issues on Nvidia, Intel and AMD.
Avoiding jank is also more or less impossible on X. There is no substitute for Wayland's "every frame is perfect" model.
Oh, and you can't connect a high DPI screen and a low DPI screen at the same time with X; to the degree that DPI scaling works at all, it's one global setting so you get to choose whether stuff should be absurdly big on your low DPI monitor or absurdly small on your high DPI monitor.
Comments
Writing a Wayland compositor on top of wlroots is probably a larger project than writing a window manager for X. But it's not orders of magnitude, wlroots handles a whole lot of the dirty work for you.
It actually does. The protocol doesn't handle things we expect from modern hardware and software. And the implementation certainly rots away as the rest of the software ecosystem changes in ways which will slowly make Xorg more and more broken. Drivers will change in ways which expose Xorg bugs. GUI toolkits will introduce bugs in their X backends and introduce new features which don't work on their X backend. Nobody maintains X anymore, and something like a display server in a rapidly changing software and hardware ecosystem requires maintenance to keep functioning.
None of this is to say the Xmonad developer should spend time rewriting their project to use wlroots instead of X. But as long as it requires X, it's living om borrowed time.
There is not one singular meaningful app or feature that doesn't work on X at this point.
Screen tearing is more or less unavoidable on X. I've had tearing issues on Nvidia, Intel and AMD.
Avoiding jank is also more or less impossible on X. There is no substitute for Wayland's "every frame is perfect" model.
Oh, and you can't connect a high DPI screen and a low DPI screen at the same time with X; to the degree that DPI scaling works at all, it's one global setting so you get to choose whether stuff should be absurdly big on your low DPI monitor or absurdly small on your high DPI monitor.
I didn't have that problem is 2003 nor today.
Good for you! Doesn't make them not problems.