I don't have any issue with Asahi focusing on Wayland first. But this attitude doesn't make me feel great. Is it really so difficult to have a little bit of empathy for your end users?
I don't have any issue with Asahi focusing on Wayland first. But this attitude doesn't make me feel great. Is it really so difficult to have a little bit of empathy for your end users?
That’s easy to say if you’ve never worked on Xorg. The codebase is one of the worst in existence, few people fully understand it, and fixing bugs in it is a modern Sisyphean wheel.
- GNOME is Wayland by default
- Red Hat has announced Xorg is depreciated. A big deal considering they were basically keeping Xorg on life support single-handedly. Without Red Hat, there’s basically nobody working on it anymore.
- KDE Plasma 6 has announced Wayland is default now.
At some point, it becomes like a user complaining that OS/2 is no longer supported. It’s dead, X11 is older than OS/2 (June 1984!), we are all collectively exhausted, time to move on.
If xmonad doesn’t work for your system; take it up with them.
The users will move on when the replacement is unambiguously better, and/or at least has feature parity. Telling someone to throw out their working setup is a lot of why Wayland is viewed by some people with derision.
> 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.
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.