Linux

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.

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

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

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.

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.

Yes, though "since when" depends on the machine. My last machine to switch over was one with an NVIDIA GPU a couple of months ago.

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.

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 have for more than a year. I've never had a single problem, but I'm on an all AMD system.

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

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.

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.

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 don't use it because it makes blender run at like 5 fps for some reason.

I use it with gnome on nixos without any problems AFAICT. Had the explicit sync issue with Nvidia initially but I ended up buying an rx6800 to use as the host GPU when I set up win11 with KVM. Been completely fine since.

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