Linux

I've been on Sway for a while now. Also have a computer on Plasma (Wayland).

(Intel iGPU, AMD APU, and AMD graphics card)

I'm on AMD, so I've been on Wayland since around 2021. Haven't really experienced any issues.

KDE Wayland is an epilepsy inducing flickerfest with my Nvidia GPU, so it's off limits until they fix it. Games usually run fine on X11, but one exception I noticed is Noita, it runs like crap on X11, and runs great on Wayland for some reason.

Plasma 6 fixed a lot of issues I had with Wayland, mostly multi monitor, but I've been using it since steam on X11 would cause your entire desktop environment to freeze up consistently every time. I read it was because steam was constantly pinging your display ports to see if there was another monitor connected, but I don't know how true that is. Moving to Wayland fixed that probably because of xwayland

Used it for the last few years. X just doesn't work right with multiple monitors of different resolution.

I've been using it since Plasma 6 came out so about 3-4 weeks.

Overall, it's been a very negative experience for me. The main problems have been:

• Random scaling issues in apps: some apps show a slightly smaller cursor, other show a poorly upscaled one, others have random rendering issues like lines remaining on the screen after an option is no longer highlighted (gimp, libreoffice, many others), some apps have random flickering of parts of the UI, some apps no longer scale at all or are scaled twice. Plasmashell itself has blurry icons on the desktop but all other KDE apps don't. I know fractional scaling has always been problematic, but it has gotten worse to the point of being almost unusable
• Random crashes of GTK apps when using the wayland backend. Some GTK apps don't even start and segfault immediately with a wayland error in the terminal
• Some apps like okular and libreoffice lag like crazy or outright freeze when scrolling
• Some games not capturing the cursor properly (Proton)
• Inconsistent font rendering, some fonts look fine in some apps and atrocious in others
• Issues when resizing or moving windows, some times they "jerk" off the screen or resize to a very tiny window and I'm forced to use key combinations to resize them again
• Random issues with window decoration not appearing in some apps but randomy appearing for things like context menus

This is on a full AMD system with Arch Linux, the latest kernel and mesa-git. I hope for KDE's sake that there's something broken in my installation because I can't believe the KDE team released Plasma 6 in this sorry state.

I use it with gnome on nixos without any problems AFAICT. Had the explicit sync issue with Nvidia initially but I ended up buying an rx6800 to use as the host GPU when I set up win11 with KVM. Been completely fine since.

I'll probably make the jump when Plasma 6.1 releases with their "real, fake session restore" functionality, was hoping that would make it in to Plasma 6, and I am daily driving Wayland on my laptop now, but I kinda need my programs (or at least file managers and terminal windows) to re-open the way they were between reboots.

Thanks to kscreen-doctor, I've been able to port most of my desktop scripts that I use for managing my multiple monitors to work on Wayland, and krdc/krfb have been a decent enough replacement for x11vnc or x2go for accessing the desktop on my home server/NAS remotely (I know, desktops on servers are considered sacrilege, but for me it's been useful too many times to get rid of at this point).

Where Wayland currently shines for me is VR, Steam VR works better, and more consistently on Plasma Wayland than X11 at this point, which is probably more of a Valve thing than a Wayland thing. When I first got my Index, X11 worked fine, but there have been times when Steam VR on Linux being "broken" has made the news on Phoronix/Gaming on Linux, but still worked fine on Plasma Wayland (which seems to be where Valve is doing most of their SteamVR Linux testing as of late).

As an end user, I do wish that the Wayland specification was organized better, because as an outsider, it seems a lot of the bickering that goes on has more to do with everyone having different end goals. I think if they would split out the different styles of window management to have their own sub-specs or extensions and then figure out what of that could be moved into the core after everyone has built what they need would be better than their current approach of compromising their way through every little decision that doesn't always make sense for every use case. Work together when it makes sense, but understand that there are times when that doesn't make sense, and sometimes you can't please every stick in the mud, and are going to have to do your own thing without them. I do get the appeal of doing things right the first time too though, even if it takes more time. But it seems like usability is always the thing that gets sacrificed when compromises are made.

I had it on a test system and Chrome/Chromium wasn't happy. Slow af. Dunno if it had an impact on Firefox, but that used a lot of RAM and was very slow when sharing the screen.

At least Waydroid worked flawlessly 👍

For now, I'm back on X11 where I game. I'll just wait for it come by default on major distros ("stable"), wait a little longer (stable for real) and then switch once nothing on my system needs "XWayland" or whatever. wine does AFAIK, so at least due to that, no Wayland for me.

CC BY-NC-SA 4.0

I'll switch to wayland when it runs better than X. And that isn't the case for now.

I will daily drive Wayland when it becomes Xorg function equivalent e.g. functional screen capture and overlays like every other OS (so never)