KDE

I will preface that Xorg is obviously an unmaintainable mess of legacy decisions and legacy code, and I have both a machine that runs Hyprland and a machine that usually starts Plasma in Wayland mode so the Wayland situation getting to be more-or-less adequate with persistent irritations here and there... but Wayland is trauma-driven-development. It's former xorg developers minimizing their level of responsibility for actual platform code, but controlling the protocol spec, and in the position to give up on X in time with their preferred successor.

Essentially all of the platform is being outsourced to other libraries and toolkits, who are all doing their own incompatible things (Which is why we have like 8 xdg-desktop-portal back-ends with different sets of deficiencies, because portals were probably designed at the wrong level of abstraction), and all have to figure out how to work around the limitations in the protocols. Or they can spend years bikeshedding about extensions over theoretical security concerns in features that every other remotely modern platform supports.

Some of that outsourcing has been extremely successful, like Pipewire.

Some attempts have been less successful, like the ongoing lack of a reasonable way to handle input plumbing in a Wayland environment (think auto-type and network kvm functionality) because they seem to have imagined their libinput prototype spun out of Weston would serve as complete generic input plumbing, and it's barely adequate for common hardware devices - hopefully it's not too late to get something adequate widely standardized upon, but I'm increasingly afraid we missed the window of opportunity.

Some things that had to be standardized to actually work - like session management - have been intentionally abdicated, and now KDE and Gnome have each become married to their own mutually-incompatible half solution, so we're probably boned on that ever working properly until the next "start over to escape our old bad decisions" cycle.... which, if history holds, isn't that far away.

We're 15 years in to Wayland, and only in the last few years has it made it from "barely a tech demo" through "Linux in the early 2000s" broken, and in the last year to "problems with specific features" broken ... and it is only 4 years younger than the xf86->xorg fork.

X11 was dead walking a long time ago. Not enough people put in the effort for Wayland earlier an now they are shocked there are bits missing.

Wayland didn't break everything, but Nvidia 545 certainly did

Wayland isn't perfect, but it's definitely getting there.

I think one of the biggest migration problems is that things have to move from the windowing system to the desktop environments, and they're slowly adapting to it.

https://en.m.wikipedia.org/wiki/Betteridge's_law_of_headlines

I've been wondering for a while if Wayland supports remote display like X11/Xorg did

For me, yes: Wayland doesn't work at all and the only answer I can get is that it's because of Nvidia. That's stupid because until some update broke it, it worked. Most apps were just very buggy.

Fantastic read

as long as software I use daily doesn't work on it as transparently as it did to me as an end user on xorg then yes, to me as the enduser, Wayland does break things and no, Wayland is not ready

I am an enduser. I don't care about the specifics, I expect things to work and not suddenly break.

For all the "year of the linux desktop" shouting, nobody wants to truly really think about or consider non-dev daily driver endusers who just want things to continue to work like they always have

@leopold my only issue was that nvidia won't recover if screen goes to sleep. I fixed it by not letting kde to put screen to sleep :hamster_dance:

lokalize (Translation tool) is, only application for me, not working with Wayland at all (There is bug reported about it). I am using KDE with Wayland on my daily laptop.