Linux

I have a laptop that has an AMD embedded GPU for the desktop environment, and an Nvidia GPU for playing games. I have been using Wayland since plasma 6 hit Tumbleweed maybe a week and a half ago. So far I've had zero issues, likely because I'm using my AMD graphics all the time (I haven't played games on my laptop since I switched to Wayland)

@headroom Wayland has been my daily for almost a year-and-a-half, most of that on Intel/Nvidia hybrid gpus. I used to use XFCE but switched to Plasma in anticipation of the Landing of Way.

I've been using wayland almost exclusively since 2020 because x-org doesn't support multi refresh rate setups and it was driving me nuts to have everything run at 60hz. It's been pretty smooth sailing because I use an AMD gpu. I have to admit that steam is indeed a lot buggier under wayland, I try to use gamescope for every game as that fixes most problems I have with them. My hope is that proton will use wayland for most games by the end of this or next year.

For about 3-4 years. I switched after sway added support for per-display VRR which xorg cannot do still (and probably will never be able to do due to core design limitations)

On AMD it's been better than Xorg for a couple years now in my use case. No more tearing and latency issues, any games that don't play nice have worked fine with gamescope.

With HDR support finally on the horizon it'll be able to completely replace windows for me which I already barely use.

The only issue I regularly encounter is programs handling windowing strangely. Some programs like to switch themselves into my active workspace under certain circumstances which is mildly annoying but just requires that I press the hotkey to put them back where they belong a couple times a day.

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.

My Thinkpad touchscreens were useless until I switched to wayland.

The only drawback is I have to manually edit the qgis desktop file to start qgis with x11 instead of Wayland. I had to do the same to a couple other random experimental apps, too.

I've switched nearly all my computers to Linux with wayland in the past 2 years with the last device coming over in the last couple of months.

I run a headless fedora/kde ~~/wayland~~ gaming desktop (with a nvidia GPU) which I use exclusively over steam links dotted around the house. That took a bit of tinkering tbh but flawless operation since. Edit: Turns out its actually still on Xorg. Still some work to do here getting this moved over. I forget why I didn't stick but must've been some combination of headless and steam link streams

I use arch/hyprland on my daily driver laptop and arch/sway on my work laptop.

The wifes laptop is also fedora/KDE on wayland.

Wayland has been very stable for me since 2021, never went back to X.

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

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

When I'm forced to, and not before then. X works perfectly well so there's no reason for me to switch to something else with less features.

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

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.

I am dependent on a couple of programs I run via wine - and wine still isn't directly compatible with wayland and buggy with xwayland...

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

Been using it since plasma 6

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.

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 use Sway exclusively on my personal systems. For work, I have to use Zoom, and you can't share your screen on Zoom if you're using Wayland. So I use xorg-server and i3.

Aside from Zoom, the only thing I wish would support Wayland better is ffmpeg. There are janky workarounds to make ffmpeg capture from Wayland, but they're... well, janky workarounds. If I abolutely have to capture video from my desktop, I switch to xorg-server/i3 long enough to do that then go back to Sway.

I'll switch to Wayland on my work machine when Zoom supports it. And I guess the ffmpeg thing, while unfortunate, isn't enough of a deal breaker to keep me from daily-driving Wayland.

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

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

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.

Tried wayland but it doesnt work on debian stable + kde + nvidia hickup-free yet. I will switch when a) the fixes come to stable and b) a need to switch arises.

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.

Not yet. I'll give it another go when I get Plasma 6 (I'm on Debian, so either I'll switch to Sid or just wait a while).

Last time I tried it, it mostly worked, but mpv had some issues and missing features on Wayland. I haven't kept up with the mpv developments since then so I'm not sure if that's been addressed upstream yet.

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

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.

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