Linux

Since Fedora 35 or more specifically rawhide in the lead up to Fedora 36, so late 2021. Plasma Wayland session, it had some rough edges, but I found it tolerable. I understand some people wont put up with it, or find workarounds and that is fair. Its been good to experience it as it has matured.

I've been daily-driving hyprland for the last couple of months and it's been very smooth sailing for me. I configured it to very closely resemble my bspwm - polybar config though it was easier to set up. I have to say that in 99% of cases the experience is equivalent. You also get to run Wayland exclusive applications (though those aren't really common).

When network keyboard and mouse sharing works. It is the only thing stopping me going full Wayland.

I tried Wayland out again last week and all it did was make my monitors flash white and black over and over again. Couldn't get it to stop unless I restarted. No idea how to fix that since I can't even do anything past the sign in screen lol. Maybe one day it'll work.

I am a relatively new Linux user, 3 years (almost 2 years dual booted with Windows and now only Linux) and I started using Wayland after approx 2.5 years ago. I used it on my ideapad gaming with 3050etx and Intel igpu and prior to that I used some hp laptop... With gtx 980mx. I used manjaro then arch and then fedora for the last yeae mostly and I haven't encountered any issues with Wayland whatsoever

I've been using it since it felt usable enough in GNOME to me. Around 2015-ish, give or take a year. GNOME leading on Wayland support is a big part of why I switched to it from Xfce back then. Nowadays KDE and others have plenty good Wayland support too (better in some ways like allowing server-side decorations and global shortcuts) but I just haven't felt like trying to properly experiment to see what I like.

I've always avoided Nvidia on my desktops. Stuck with either radeon or intel and never had any exceptionally big issues with them on Wayland. Though other things like hardware accelerated video decoding have had a history of being spotty on some drivers/GPUs.

Generally I have when I use Gnome or KDE on Linux, though I have started to prefer MATE, which doesn't have Wayland support yet afaik. I also started using FreeBSD on one of my computers a bit more, and I believe Wayland support is still a bit wonky on that right now. But as soon as Wayland support is there I'm definitely switching to that on the daily.

Been on it for about a year now, both with my desktop's A770 and my laptop's AMD iGPU. Experience has been pretty much flawless.

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.

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

I use Wayland on my laptop running fedora 39 kde spin and it mostly runs fine. When I browse gifs in discord the screen flashes white and I can't maximize jellyfin on connected TVs but other than that no major issues.

I have been for the past month now. All of my games are now working.

Previously no and the reason was bc of Nvidia issues, but they all seem resolved now for the most part

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.

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.

Been using it since plasma 6

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.

No, I see no benefits

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.

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 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 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.

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.

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 🤷

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.

Using Wayland with KDE Plasma 6 on Arch btw. But I installed the old NVIDIA driver 535, waiting for explicit sync in 555 to fix flickering in games.