Linux

Full AMD. KDE. Only one issue. I RDP into my work laptop, and sometimes I get weird artifacts on the screen until I minimize/maximize. Everything else is flawless

When my DE, Budgie, supports it. I'm not too bothered about using it, with a beast monitor and a high-end PC I hardly notice the X.Org quirks.

I'll take it as when Budgie is ready to ship a full Wayland-only experience, I'll be ready to use one.

When I can use mtp connections with cli apps instead of only gui apps

Probably like 3+ years on the laptop (Intel), approaching 1 year on the desktop (AMD).

Wayland + NVIDIA is still a disaster and a very inferior experience compared to the AMD side. I would stick with Xorg if I had NVIDIA too.

Only on Intel or AMD do you get a Wayland experience that makes you go "wow I can't wait for Xorg to be dead for good". I had a very, very noticeable improvement even years ago on Wayland when it comes to triple monitor performance, VRR and vsync in general. Now that screen capture and stuff is mostly figured out, it works perfectly for me.

At this point my only issues with Wayland are related to features that haven't been implemented yet, not bugs or performance issues. And I'm more than willing to workaround the limitations and take the benefits.

I've been patiently following development and waiting to switch for 10 years, first exploring Wayland with the EGLStream patch for Weston on my GTX 580. Even back then you could feel the difference, but obviously it was also unusable other than demos.

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.

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

Been using it since plasma 6

Mid 2022, when i swapped my nvidia card to an AMD one. Instantly switched to Wayland (KDE Plasma) and stayed there.

I don't feel like fighting my OS. It locked up every time it went to sleep and I switched to X and the problem went away. Maybe I'll try again but why bother? Everything is working fine for me.

Niche, I know, but I'm waiting on full functionality in Input Leap (Barrier fork which was a Synergy 1.x fork). Right now it sounds like it's 90% of the way there but lacks clipboard sharing. I'm running Wayland on my desktop, but this soft kvm is pretty fundamental to my workflow on my laptop.

Yes. Since 2013 or so, if I remember correctly. Gnome 3.10.

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

KDE Plasma on Arch on integrated Intel graphics here. I've been on it for a few years and I love it.

i'll probably jump the next time i change window managers or distros... i havent a reason to currently

I've been using Sway on and off since 2020. Wayland always worked well as long as it supports the specific use case and the apps are doing the right thing (e.g. pipewire, portals, no Xwayland).

VRR with multiple monitors and HDR are likely the biggest reasons to use Wayland, as most other improvements are less noticeable. E.g. Sway always felt more responsive to me than i3 + picom, even with a single monitor in 2020.

If you have issues with applications not working well on Wayland, either wait for proper Wayland support or ditch them. For Steam this'd likely mean stay on X.org.

I've been using Hyprland for about 2 years. I did have some issues with screen sharing (teams, discord) and some steam games (non native, with proton) need some extra launch parameters, but they all work now. Over time I was able to fix all the little issues. For me Hyprland is a daily driver, but I like to tinker. I can see how this is not for everyone.

I haven't touched the X11 session once since I got my laptop, all Wayland

I only use wayland on my t480 and it makes a noticeable difference on that machine, but not on my desktop with Nvidia. I have been testing it for a couple of days on my Nvidia box though. So far I've found it mostly works better than I expected but some games played on Nvidia+Wayland makes it look like my monitor is about to die with the weird flickers it does at times and under certain conditions (like loading screens it's unbearable), otherwise performance is good and seems to lock in at 144hz. Also does anyone know why there are no settings in the nvidia-settings app under Wayland?

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

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.

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'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'm running Wayland for many months now. Yust because why not. It just works. Debian sid with gnome here.

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.

A year-ish, Plasma, Intel iGPU for Desktop and Nvidia offload for Steam. It's great.

Got hyprland running on the macbook, have tested it out on desktop. Not quite the daily driver, plasma 6 on X is still the norm there, but I think as soon as synergy works in Wayland I’ll make the switch everywhere

Whenever Nobara moves to KDE 6, I'll probs switch over to Wayland. Likely sometime this year.

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.

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.