Linux

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.

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)

I only use wayland on my t480 and it makes a noticeable difference on that machine, but not on my desktop with Nvidia. I have been testing it for a couple of days on my Nvidia box though. So far I've found it mostly works better than I expected but some games played on Nvidia+Wayland makes it look like my monitor is about to die with the weird flickers it does at times and under certain conditions (like loading screens it's unbearable), otherwise performance is good and seems to lock in at 144hz. Also does anyone know why there are no settings in the nvidia-settings app under Wayland?

I don't. And I will when it actually fucking works.

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.

I haven't used Wayland for about a week overall in my year of using Linux.

Full AMD. KDE. Only one issue. I RDP into my work laptop, and sometimes I get weird artifacts on the screen until I minimize/maximize. Everything else is flawless

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.

No, I see no benefits

Been using it since plasma 6

i'll probably jump the next time i change window managers or distros... i havent a reason to currently

I haven't touched the X11 session once since I got my laptop, all Wayland

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.

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.

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.

Have been using GNOME with Wayland on a dual GPU NVIDIA laptop for 2 years. DE runs on the integrated Intel card; Steam, games, anything that needs dGPU runs on NVIDIA. It’s been a smooth experience.

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.

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

Yes. Since 2013 or so, if I remember correctly. Gnome 3.10.

A year and a half? Basically when hyprland got good enough. I used to use awesome and needed something with similar pretty features.

I could switch tomorrow if I could do my current setup:

• Tiling Window manager (sway?)
• simple status bar to output text from a script with clickable applet icons (waybar?)
• the way to show/hide windows on a button press - I have a script that I use to quickly toggle 3 dropdown terminal windows

Last time I tried Wayland in December, I had issues with waybar not supporting clicking tray applet icons. Also I've ported my dropdown terminals script to support sway - and it worked half the time, like, literally every second key press was ignored.

On one hand I have X session that currently has no downsides for me, on other - wayland that has no upsides. Tell me, why would I switch?

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.

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.

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

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.

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

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.

I have a laptop with integrated Intel graphics and a desktop with Nvidia graphics. I use Wayland on the former right now as of KDE 6. I have noticed some odd behaviors, but overall it has been fine. The latter, however, just boots to a black screen. I have neither the time nor the desire to debug that right now, so I will adopt Wayland on that machine when it works with Nvidia to a reasonable degree of stability.

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.

No. I plan to switch when I replace my 3070 with an AMD chip.

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.