Linux

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.

When I can inject keystrokes to windows not on focus with scripts.

I've been daily driving it on some devices for maybe 6 months.

My only showstopper was input-leap, but I have not had to use it for two months. So I've gone all-in since. It works better in every sense - except for the input-leap thing.

I have a laptop with integrated Intel graphics and a desktop with Nvidia graphics. I use Wayland on the former right now as of KDE 6. I have noticed some odd behaviors, but overall it has been fine. The latter, however, just boots to a black screen. I have neither the time nor the desire to debug that right now, so I will adopt Wayland on that machine when it works with Nvidia to a reasonable degree of stability.

I've been using it since about spring 2022 and it's been way more reliable than X for me. The only times I've had trouble was one computer where I was missing one of the pipewire packages I needed for screen sharing and another time I tried to run it on a 20 year old Radeon X1600, but both of those were my fault and not something a normal user is likely to encounter. For context I've used Sway, Hyprland, GNOME, and Plasma although the usability has been the same between all of them.

I tried it a few times on different hardware. There were weird lags, freezes, crashes, latency, artifacts, flickering (once I had to reinstall the system to fix it), no cursor in games etc etc so no thanks. It doesn't work for me. Maybe it's possible to fix if I spend a week in the terminal but ehh idk. It's just not ready for me I guess. And I didn't even have enough time to find compatibility issues. I'm a little bit afraid that by the time Wayland is ready, a new system will already be required lol. It's getting better though so probably it will be ready for business/production in a few years idk. The only thing I can definitely tell is that it must not be the default on regular desktop distros now. Wayland may be good but it's not mature. Switching to it on the login screen is a 3 seconds task and it fixes so many issues, especially on older hardware

I'm running Wayland for many months now. Yust because why not. It just works. Debian sid with gnome here.

Been using it since plasma 6

Ye, since Plasma 5.24 I think. Used to occasionally switch to X11 for competitive gaming, but as of Plasma 6 their Wayland compositor supports fullscreen tearing, so now I have no need to use X11 anymore

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.

Every update of plasma I switch to Wayland so far my record is 1 week before running into a deal breaker issue.

Though Plasma six is so close to working for me. The only issues I'm getting on wayland is flickering in games, an issue where some windows don't show up on the task bar, awful screen tearing when using two monitors of different resolutions, keyboard lag.

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?

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 would like to, but I'm running Arch with Cinnamon, and that desktop environment only has an experimental version of Wayland implemented. I've tried it, and it's too buggy to be used as a daily driver.

Yeah, I've been using it for a few years now. Not really given me any issues so I don't have any reason to use X again, but my use case is pretty basic 🤷

I've been dailying it on my desktop for a couple of years now (I want to say since 2022 but I forget exactly... there was a Plasma release where a certain feature finally became realised on Wayland and I switched then). Been running on my laptop for much longer, where I use GNOME. It's been great, but I don't have any Nvidia hardware.