Linux

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've been on Wayland (Hyprland) for 8 months, unfortunately on Nvidia.

Switched over to wayland about 4-5 years ago, have run into a couple of problems dealing with theming, fractional scaling and of course nvidia, but on the whole my experience has been without major issues.

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

When? Since Ubuntu made it the default for non Nvidia PCs

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.

Probably like 3+ years on the laptop (Intel), approaching 1 year on the desktop (AMD).

Wayland + NVIDIA is still a disaster and a very inferior experience compared to the AMD side. I would stick with Xorg if I had NVIDIA too.

Only on Intel or AMD do you get a Wayland experience that makes you go "wow I can't wait for Xorg to be dead for good". I had a very, very noticeable improvement even years ago on Wayland when it comes to triple monitor performance, VRR and vsync in general. Now that screen capture and stuff is mostly figured out, it works perfectly for me.

At this point my only issues with Wayland are related to features that haven't been implemented yet, not bugs or performance issues. And I'm more than willing to workaround the limitations and take the benefits.

I've been patiently following development and waiting to switch for 10 years, first exploring Wayland with the EGLStream patch for Weston on my GTX 580. Even back then you could feel the difference, but obviously it was also unusable other than demos.

I don't use Wayland. I can. I've tried, but I went back to X. On Wayland, when I take a Firefox tab out of a window to make it it's own window, there's a pause of over a second until the new window appears. It drives me crazy every time. On X it's instantaneous.

I don't use two monitors, I don't use Nvidia. For everything else I use my computer for, I haven't found an advantage of using Wayland over X. So, I'll stay on X until I'm forced to change, I guess.

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

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.

KDE Plasma on Arch on integrated Intel graphics here. I've been on it for a few years and I love 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.

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.

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.

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

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

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.

I switched to Wayland to get discord streaming with audio working but now Steam remote play has issues capturing some windows unless I open Steam with the -pipewire option. Other than these issues with video streaming it’s been almost the same ir better than x11 on my AMD machine.

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.