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.

Since I mostly run Debian with KDE, I've been using it a lot since KWin is on its stable repo.

First time I really use it is on Gentoo, which exclusively runs Plasma. Since it's rolling-release, it didn't take too long to be available.

I've been moving this build from one computer to another, they all work fine. Currently it's on a Thinkpad W530. Got some problems with multi-monitor that never happen under X11. Thankfully after I replace the firmware with coreboot, and opted for dGPU only, I never encountered any issue.

Currently, what keeps me from fully ditching X11 on KDE is the buggy SDDM support.

On the other hand, I've been using Linux Mint on my work PC. As you may have known, neither Cinnamon and XFCE has it at the moment.

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

A couple years(ish) on intel-only laptops. I run it with KDE Plasma. I only think about it when I see a thread like this one.

For me it Just Works™. I recognize that being intel-only may be a contributing factor, and my certification of Just Works™ is not to imply dismissal of any problems others may be having. 🙂

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 need full screen share and I think it isn't there for wayland. But the track pad support is better in wayland.

About a year ago I moved to Hyprland & Wayfire for my NVIDIA & Intel boxes. Moved NVIDIA to Radeon a few months back and had mixed results.

Recently tried Plasma 6 for experimental HDR and am impressed.

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.

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.

Yeah, I've been using it for a few years now. Not really given me any issues so I don't have any reason to use X again, but my use case is pretty basic 🤷

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

Used it for the last few years. X just doesn't work right with multiple monitors of different resolution.

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

I’ve been using it ever since Ubuntu switched over. No major issues, though I have to launch Calibre (the ebook manager) via the command line with a special environment variable because the developer is anti-Wayland. I’m looking for alternatives.

I'm running Wayland for many months now. Yust because why not. It just works. Debian sid with gnome here.

I tried Wayland many times in the past ~6 years, usually with Sway (but I tried most other compositors, other than KDE's), but I always came back to X11 (using cwm).

Around two months ago I started using river, and I think I'll stick with it. There are enough Wayland protocols which now exist (and are supported by river) that using a minimal compositor feels pretty similar to just using a window manager on X.

When I can inject keystrokes to windows not on focus with scripts.

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.

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.