Linux

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

Since maybe 2 years and i am very happy with it. Sometimes screensharing problems but thats it.

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.

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

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.

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.

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.

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'll probably jump the next time i change window managers or distros... i havent a reason to currently

For my home workstation running Debian/Bookworm I started running Wayland-Plasma when Xorg mysteriously refused to work after replacing my video card. Wayland just worked and really had no issues for me so while I'm sure I could have solved the X11 problem I didn't have a real need to.

I also changed my laptop to Wayland-Plasma more recently. A problem I had was in setting up the right modes for external monitors on laptops but that seems to work OK now. Generally things just work.

Plasma 6 fixed a lot of issues I had with Wayland, mostly multi monitor, but I've been using it since steam on X11 would cause your entire desktop environment to freeze up consistently every time. I read it was because steam was constantly pinging your display ports to see if there was another monitor connected, but I don't know how true that is. Moving to Wayland fixed that probably because of xwayland

I've been on Sway for a while now. Also have a computer on Plasma (Wayland).

(Intel iGPU, AMD APU, and AMD graphics card)

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 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 use Wayland since I got a second monitor, since X can't handle mixed DPI. I'd use X otherwise, since global hotkeys work there

Yes, since Fedora 21 when it switched by default.

It hasn't really caused game breaking issues for me, however it is nice that the few nit-picks have all been resolved.

I get the sense that the majority of people use it on Workstations, there is just a vocal minority that resists the change. There are so many academic and enterprise users just using distros in their default state Wayland and all.

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