As much as I want to support the idea of a well supported, modernised graphical protocol system, wayland simply isn’t ready yet. There’s so much shit that simply doesn’t work, and they’re all made up of little niche cases that will take substantially longer than a few months to resolve, and I still haven’t seen anything that suggests Wayland has a practical equivalent to xorg.conf.
Is Alma Linux rolling their own version of Plasma with x11? Or are they just sticking with an older version of Plasma? Is anyone else planning on hacking x11 back into the DE?
What exactly isn’t ready? All I know is the lack of trackpad gestures and fractional scaling(even though I don’t use it) in x11. X11 is the one that feels more janky while wayland has been smooth sailing.
I’m even developing a gtk4 program, I assume if there were problems with wayland I’ve would’ve noticed it by now. On the other hand, testing my program on debian 13 with x11 did make the experience a little jankier.
Given such huge differences in reported experiences, I can only assume it’s a difference in hardware compatibility? Are some machines just better in x11 and others in wayland? Is that why everyone has such different experiences?
I don’t notice any difference in performance between x11 and Wayland, but there are some things I just haven’t been able to get working right in Wayland. Changing font DPI. Screenshots, when I want to capture a selected area and not the entire screen. Color pickers. I’ve tried several that supposedly work with Wayland, but they don’t. Screensavers. Alt-tabbing between a fullscreen game and the desktop or another window. I should mess around with it some more. I know my own distro is getting rid of x11 at some point.
Wayland has improved a lot in the last few years. And yes, there are and have been differences in hardware.
I think the biggest difference is likely to be software though. Primarily in two ways.
First, a lot of people are using older software. Not to pick on Debian but it is a good example. A Debian Stable user may be using NVIDIA drivers that are literally years older than what an Arch user is using. Paired with Wayland compositors and XDG portals that are older as well. So when they talk about Wayland (even today), they are really describing the experience from years ago.
Second, what use cases are well supported on Wayland still varies from compositor to compositor. Somebody using Plasma 6 may experience that pretty much everything just works. Somebody using Sway may find that some uses cases are still immature.
Put these together and you have a lot of NVIDIA on Debian people telling you things don’t work and a lot of AMD on Fedora people wondering what they are talking about.
Today, Wayland and Xorg are more “different” than better or worse. If you are happy with Wayland, migrating to Xorg would probably feel like a real step back and there would be all kinds of issues and deficiencies. But, for some, the reverse can still be true. Wayland still has a few gaps.
Finally, they ARE different. Which means that if you insist on trying to make Wayland work exactly like X11, it is easy to make it seem like it is not working, even if Wayland can do exactly what you need in some slightly different way.
The important thing to acknowledge though is that more than half of Linux desktop users run Wayland now. And the majority of new users start in Wayland and will never switch. So X11 is the weird one now. And while Xorg is about as good as it is ever going to be, Wayland gets better every day.