I've been using Sway for over 2 years, and for my workflow it works well, with one exception I just can't get vscode to scale properly for my display.

I daily drive wayland with nvidia and I play games modestly. I have Xorg installed as backup for when issues happen, but it's been pretty rare in the last couple months.

I've been using Wayland since the end of last year, I haven't done any real benchmarking but games run about the same for me on either.

Been running Wayland for 5 years on my development laptop (sway, Intel GPU, blacklisted the nvidia gpu). At the start I've had a couple of issues, nothing too bad. Haven't had any issues for over 2 years. Switched to Linux on my gaming PC about a year ago, KDE plasma on Wayland but do most of my gaming from a steam gamescope session. Very happy overall with Wayland, glad it exists. Sharp text on a fractionally scaled display for reading code was just too compelling at the time and it only improved.

I couldn't get the trackpad working right on X (why tf is acceleration on by default?), tried switching to Wayland in the first few hours of using Linux, and haven't had significant issues since. At that point I had no reference on performance, so no way to tell if X would be better.

There's maybe one bug that causes an unrecoverable GPU hang when using certain applications, but that may have been fixed in the kernel already, and I just need to use something newer than 22.04 LTS.

I don't use it because it makes blender run at like 5 fps for some reason.

Yes, I have Wayland on both my gaming machine and my laptop. I switched for security reasons (i.e. client input isolation). I think Wayland compositors tend to be buggier than X WMs/DEs, just because they are newer/more immature, and there is less native support for it. But some native Wayland-only programs are really good, like Foot is pretty much the perfect terminal emulator for me, being lightweight and fast but with sixel support too. It pretty much has every feature I want to use (except ligature support but that's not super important to me) without any of the features I wouldn't use (looking at you Kitty).

However the downside is the occasional program that just doesn't work on Wayland, like JetBrains IDEs, which are one of the few pieces of proprietary software I voluntarily use. JetBrains IDEs use a bunch of X hacks so they have some buggy behaviour on Xwayland. I really hope JetBrains hurries up with their native Wayland support, especially since so many DEs and distros are moving to Wayland by default now.

I also wish there were more tiling compositors out there. It seems to just be Sway, Hyprland, River, DWL, and QTile (which has a Wayland option, which is very cool). Of which I have daily driven Hyprland and River and been happy with them. I know there's others but they seem pretty obscure or abandoned and not something I'd be looking to daily drive. On X there are so many WMs for every possible use case. And of course the popular X WMs are pretty mature software; I don't remember many breaking bugs when I was on i3, but Hyprland and River are in very active development which means a new update can mean bugs of varying levels of annoying/need a workaround/need to downgrade.

I have for more than a year. I've never had a single problem, but I'm on an all AMD system.

I could switch tomorrow if I could do my current setup:

• Tiling Window manager (sway?)
• simple status bar to output text from a script with clickable applet icons (waybar?)
• the way to show/hide windows on a button press - I have a script that I use to quickly toggle 3 dropdown terminal windows

Last time I tried Wayland in December, I had issues with waybar not supporting clicking tray applet icons. Also I've ported my dropdown terminals script to support sway - and it worked half the time, like, literally every second key press was ignored.

On one hand I have X session that currently has no downsides for me, on other - wayland that has no upsides. Tell me, why would I switch?

Since I mostly run Debian with KDE, I've been using it a lot since KWin is on its stable repo.

First time I really use it is on Gentoo, which exclusively runs Plasma. Since it's rolling-release, it didn't take too long to be available.

I've been moving this build from one computer to another, they all work fine. Currently it's on a Thinkpad W530. Got some problems with multi-monitor that never happen under X11. Thankfully after I replace the firmware with coreboot, and opted for dGPU only, I never encountered any issue.

Currently, what keeps me from fully ditching X11 on KDE is the buggy SDDM support.

On the other hand, I've been using Linux Mint on my work PC. As you may have known, neither Cinnamon and XFCE has it at the moment.

About a year ago I moved to Hyprland & Wayfire for my NVIDIA & Intel boxes. Moved NVIDIA to Radeon a few months back and had mixed results.

Recently tried Plasma 6 for experimental HDR and am impressed.

Yes, though "since when" depends on the machine. My last machine to switch over was one with an NVIDIA GPU a couple of months ago.

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.

A couple years(ish) on intel-only laptops. I run it with KDE Plasma. I only think about it when I see a thread like this one.

For me it Just Works™. I recognize that being intel-only may be a contributing factor, and my certification of Just Works™ is not to imply dismissal of any problems others may be having. 🙂

Yes, since Fedora 21 when it switched by default.

It hasn't really caused game breaking issues for me, however it is nice that the few nit-picks have all been resolved.

I get the sense that the majority of people use it on Workstations, there is just a vocal minority that resists the change. There are so many academic and enterprise users just using distros in their default state Wayland and all.

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.

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

I tried Wayland many times in the past ~6 years, usually with Sway (but I tried most other compositors, other than KDE's), but I always came back to X11 (using cwm).

Around two months ago I started using river, and I think I'll stick with it. There are enough Wayland protocols which now exist (and are supported by river) that using a minimal compositor feels pretty similar to just using a window manager on X.

No, I see no benefits

I’ve been using it ever since Ubuntu switched over. No major issues, though I have to launch Calibre (the ebook manager) via the command line with a special environment variable because the developer is anti-Wayland. I’m looking for alternatives.

Have been using GNOME with Wayland on a dual GPU NVIDIA laptop for 2 years. DE runs on the integrated Intel card; Steam, games, anything that needs dGPU runs on NVIDIA. It’s been a smooth experience.

When VMWare Horizon Client (which I need for work) supports it

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.

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

I tried for a bit and it was great, no complaints. However, I was having issues getting NixOS set up as quickly as I would like, so I went back to Pop!_OS. I'm looking forward to the next release of Pop, which will have full Wayland by default.

I need full screen share and I think it isn't there for wayland. But the track pad support is better in wayland.