Linux

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

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.

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)

I'll adopt it when it becomes Linux Mint's default

I do, but I have to switch to X11 for work. I log in using VMWare Horizon Client, which technically works on Wayland, except that keyboard shortcuts and keys like Meta are caught by my desktop.

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.

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

I've been on Wayland (Hyprland) for 8 months, unfortunately on Nvidia.

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 think about a year when I switched to it to see how it was and then forgot I had.

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.

When network keyboard and mouse sharing works. It is the only thing stopping me going full Wayland.

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.

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

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 I can use mtp connections with cli apps instead of only gui apps

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.

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.

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.

About five years with Wayland now. Started with sway and now running KDE Plasma 6. It is snappy, simple and definitely so good I will not miss X11.

(I also think systemd is cool, you can crucify me now)

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

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.

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.

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

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.

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.

No, I see no benefits