Guilty as charged

Protip: People who have iGPU + nvidia can just set the iGPU as main GPU on the BIOS and offload 3D programs to the nvidia via prime-run like they would on a laptop.

That's my setup.

And the network transparency argument is long gone. While you can indeed network windows over the wire, most toolkits use client side rendering/decorations. So you're just sending bloated pixmaps across the wire when things like RDP , VNC, etc deal better with compression, damage to the window, etc. And anything relying or accelerated with DRI3 is just NOT network transparent.

Most modern toolkits have moved past X11 because the X protocol was severely lacking, and there wasn't a good way as a committee to modify the protocol in an unified manner. I mean look at the entire moving Earth that it took for XFixes and Damage extensions. Toolkits wanted deep access to the underlying hardware and so they would go out of their way to work around X, because it just could not keep up.

The issue with wayland is that both the process and the base mechanisms had significqnt flaws, that made it take a long time to get things working. In all fairness, the core team uad a valiant effort for a dwcade, hampered by unresponsive complainers, and late-to-the-party suggestions.

Fyi: I am an early WL adopter, but not on any of the major DEs.

There's probably a lot of people on 'stable' distros who are still running Wayland code from a couple of years ago and hitting bugs that have been fixed already.

The software you use working correctly is kind of a big deal, though.

Wayland is like how windows people say Linux is.

It works and is Incredible, but on X11 things just work.

Even HDR is still “beta” on KDE iirc.

That's a weird comparison because HDR is never going to happen on X.org (nor probably in the X11 protocol or clients). Wayland is being actively developed and the developers took it from something that can be made to work with some effort and some concessions to something that will reliably work in most cases. The year isn't 1987 -- software isn't being written by nerds for nerds who can tinker and fix issues or add new features as a patchwork of unmaintainable code.

KDE on Wayland has only very recently started to become workable for me, before that it was utter crap as I switch between home and office with my laptop, with varying display setups. In that case you got stuff like screen positions not being remembered and applications consistently starting off screen, requiring gymnastics to coax them onto a display.

And regularly it would crap out and not show output to one of the displays, if you opened up display manager you'd see the displays not touching and a big red error telling you that gaps betweens displays aren't supported. Well here's a brilliant idea, how about not automatically putting a gap between them in that case?

As I said, last few months it works better (although I still encounter some issues from time to time that I never had on X11). But the whole Wayland protocol had such a rough start, with issues encountered often being downplayed by parts of the community because "it's better and we don't want to hear otherwise", that I simply cannot feel any love for it anymore. There was too much basic stuff that took too long to support, while people were shouting "but HDR!", "better code!". I don't fucking care, I just want to be able to work and for too long that required X11.

Edit: some typo's and improved readability.

You'll only see when you open your xeyes.

Wayland provides a simplified, streamlined pipeline for graphics. Lower latency, higher frame rates, less overhead. X is straight out of the late 80s and 90s. Modern X has been cobbled together to work surprisingly well. But that old architecture is what is holding it back today.