And so it begins; the forced migration to Wayland brought about from users not willingly switching to a half-baked solution from their existing working X11 environment.
Curious timing with everyone starting to drop X11 couple of weeks after a fork of X11 was announced. Almost like the announcement put a fire under some behinds to quickly get rid off X11 before the fork starts eating Wayland's lunch.
The publishing of v1.0 of a protocol has little to do with the stability of software implementing that protocol. The software in question is in fact KWin, the KDE window manager. It is the most mature and featureful Wayland compositor, and the KDE devs have done a lot of work over the past few years to get it competitive with its X11 backend. However even they themselves still consider this a transitional phase: https://www.phoronix.com/news/KDE-Wayland-Is-The-Future
Also, time is in any case less relevant that developer hours. Were I feeling snarkier, I might point out that GNU/Hurd was first released in 1990 - perhaps we can finally switch to that...
We recently swapped RPIs with Windows mini-PCs due to xdotool disappearing, and whatever the alternative is called... segfaulting. Keep going like this.
Hey Xorg, your code is like, the worst in the entire galaxy spanning the entire history of mankind will you let contributors fix it?
"No" -Xorg
Hey Xorg, it's 2025 and people have really powerful GPUs so fancy-smanchy effects can be implemented that use like 1% of a GPU's horsepower but would have been considered impossible fantasy beyond the power of every supercomputer in the world combined when you were written, can you implement something to handle stuff like that?
"No" -Xorg
Hey Xorg, your code is so insecure that any instance of it should be considered a critical vulnerability of the highest severity level will you let more than the dozen or so people you have work on it?
"No" -Xorg
Hey Xorg why do my windows get all jaggedy and messed up when I wiggle that around?
"No, uh, I mean, that's called screen tearing and it's a feature" -Xorg
Hey Xorg I have three monitors and I want to run them at different resolutions, refresh rates, and fractional scaling levels. Can I do tha..
"What the hell kind of frame buffer do you have that lets you do that?" -Xorg
Hey Xorg I was going to ask if I could do that without touching any config files or using the command line because I ain't got time for that. Wait. Frame buffer? Is this 1993? Are you developing on a single headed TurboGX-equipped Sun SparcStation running the SPARC port of Linux and you have absolutely no clue about either the state of the art or the march of progress?
My understanding is that most of those issues stem from Xorg's core design not really being compatible with modern hardware and the only way to fix it requires breaking all clients.
Readit News
I'm sitting on my porch just absolutely cackling. Y'all are hilarious.
Also, time is in any case less relevant that developer hours. Were I feeling snarkier, I might point out that GNU/Hurd was first released in 1990 - perhaps we can finally switch to that...
I don't understand why anyone thinks this is a good thing. It's been THIRTEEN YEARS and Wayland is not even close to a viable replacement for X.
"No" -Xorg
Hey Xorg, it's 2025 and people have really powerful GPUs so fancy-smanchy effects can be implemented that use like 1% of a GPU's horsepower but would have been considered impossible fantasy beyond the power of every supercomputer in the world combined when you were written, can you implement something to handle stuff like that?
"No" -Xorg
Hey Xorg, your code is so insecure that any instance of it should be considered a critical vulnerability of the highest severity level will you let more than the dozen or so people you have work on it?
"No" -Xorg
Hey Xorg why do my windows get all jaggedy and messed up when I wiggle that around?
"No, uh, I mean, that's called screen tearing and it's a feature" -Xorg
Hey Xorg I have three monitors and I want to run them at different resolutions, refresh rates, and fractional scaling levels. Can I do tha..
"What the hell kind of frame buffer do you have that lets you do that?" -Xorg
Hey Xorg I was going to ask if I could do that without touching any config files or using the command line because I ain't got time for that. Wait. Frame buffer? Is this 1993? Are you developing on a single headed TurboGX-equipped Sun SparcStation running the SPARC port of Linux and you have absolutely no clue about either the state of the art or the march of progress?
"Yes" -Xorg
"Wait, why are people abandoning me?" -Xorg
Yes. That's correct. You are correct. It is no longer fit for purpose and hasn't been for a long time. But inertia.
> the only way to fix it requires breaking all clients
Do it.
Rip the OpenVMS, SVR4, and HP/UX roots out of the ground and throw them in the trash, next to telnet and SysV filesystem support in the kernel.