Linux

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

In 2017 I bought a ThinkPad with a hidpi screen, which I knew would give me trouble with Linux. Fortunately the Fedora 26 beta had just been released and was using Wayland by default (I wasn't very Linux savvy to do it myself yet). I've been using Wayland on Fedora ever since without issue.

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.

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

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.

I know I have used it since Fedora made it default in 2016. I think I actually used it a while before that, but I don't have any thing to help me pin down the exact time.

Since I only use Intel built-in GPU, everything have worked pretty well. The few times I needed to share my screen, I had to logout and login to an X session. However, that was solved a couple of years ago. Now, I just wait for Java to get proper Wayland support, so I fully can ditch X for my daily use and get to take advantage of multi DPI capabilities of Wayland.

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

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

I haven't used Wayland for about a week overall in my year of using Linux.

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.

A year and a half? Basically when hyprland got good enough. I used to use awesome and needed something with similar pretty features.

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.

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.

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 maybe 2 years and i am very happy with it. Sometimes screensharing problems but thats it.

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?

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 haven't touched the X11 session once since I got my laptop, all Wayland

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.

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.

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 use multiple machines. On one of the core machines, I switched to Plasma 6 on Wayland when that was released. I used XFCE on X11 previously. It seems ok so far.

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.

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

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