I’ve been on Wayland for the past two years exclusively (Nvidia).
I thought it was okay for the most part but then I had to switch to an X session recently. The experience felt about the same. Out of curiosity, I played a couple of games and realized they worked much better. Steam doesn’t go nuts either.
Made me think maybe people aren’t actually adopting it that aggressively despite the constant coverage in the community. And that maybe I should just go back.
I’ve been using it on Ubuntu 22.04 for almost 2 years. It started off rocky, with frequent restarts needed, maybe every week or two. It’s been pretty solid, though I did give up on using it for screen sharing and captures, which is unfortunate timing in today’s WFH world.
Daily drove wayland back in November when I finally built my new desktop and installed Nobara. It’s the default and it juat worked out of the box. Have always been a windows user until now.
Games workost of the time. Good enough for me. Full team Red build inside the case.
Been daily driving sway for over 5 years now. There were a few problems along the way. I used to have JWM and then XFCE as a back up in case wayland fails. I really only need to go into them when there’s a need for screen sharing. But then, I mostly live in terminal and browser. Low graphic games I play seems okay. The most demanding one I played is probably Starcraft 2 and it plays well even on my crappy 7 years old laptop with intel graphics.
I wanted to love Wayland but the fact is half of the apps I use are either too small in the UI or too blurry when scaled up. Until that’s fixed I’m staying on x11 begrudgingly.
I have these exact same issues with wayland on KDE.
Yep running kubuntu and I’m a xorg boi for a while still
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.
I switched to sway from i3 about 5 years ago. It’s easier to configure (no /etc/X11 nonsense) and it fixed my screen tearing issue. I’m not much of a gamer, so can’t comment on that. Supertuxkart and browser games work fine.
Exact same. Sway’s 1.0 release was March of 2019, and it did everything I needed.
Even playing games on my desktop, Xwayland worked fine for me.
Is Sway like a Wayland equivalent of i3? That’s the only thing really keeping me on X
Yes, sway presents itself as a drop-in replacement for i3 (just built on top of wayland instead of xorg).
I’ve used it on a Thinkpad laptop for close to 4 years, and on my desktop for the past 3.
The only problems I’ve encountered are some apps not being Wayland-compatible; xwayland makes the rendering work for those but then things like sharing a window or the entire screen don’t always work. Notably, Discord’s sharing doesn’t work, but I can use OBS to record any entire screen since [the OBS devs] put in the work to properly support Wayland.
Oh interesting! I actually found Wayland to have a bit of an edge vs X. I just didn’t like the Unity environment from Ubuntu so I’ve been using i3.
I’ll have to give Sway a try
My Thinkpad touchscreens were useless until I switched to wayland.
The only drawback is I have to manually edit the qgis desktop file to start qgis with x11 instead of Wayland. I had to do the same to a couple other random experimental apps, too.
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).
deleted by creator
That’s because their mid-2000’s setup with single 1024x768 screen works just fine with compositing disabled, 24bit color depth via VGA connector.
I had to switch to Wayland the moment I tried to run simple 4K@60 on my old RX570, and Xorg was just refusing to set the mode, or produced some colorful vomit garbage when forced to do so, no matter what. And Wayland (just like Windows) simply worked.
Was it perfectly ready back then? Heck no. Is it ready now? Maybe not for everyone, but it’s getting there and time is telling us that the missing parts on Wayland side are fixable.
Criticism is viable to some degree, though. Because from the very beginning there were certain assumptions made, and creators of the base protocol didn’t care about real world use on desktop as much as they cared about the security model, it takes a lot of time to solve some of those. The development is slow and there are always some gaps here and there, but I watch it long enough (17 years) to know that to some degree it is like that with the entire ecosystem, let alone Xorg that no programmer wants to touch anymore for anything but simple bugfix or security patching.
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?
No. I’ll use it when it’s stable enough for Debian to merge it.
Possibly in 5 years?
Debian’s wiki states that “Wayland is used by default in Debian 10 and newer” (on gnome, It’s also the the default for plasma 6 but that’ll take some time to get into debian as you say)
Gsync doesn’t work yet so… Not yet for me.
Also, they need to fix the load apps in last location like X has
Every day on all my computers. No interest in going back to X11, things work better on wayland, multimonitor doesn’t shit itself randomly anymore.
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.
input-leap
this software has wayland support already https://github.com/input-leap/input-leap/issues/109
Cool.
Last I checked kwin was still waiting for some protocols to become available. I’m sure it’ll be good to go if and when I need another Mac on my desk to synergize.
There was another server that already supported wayland/gnome, but the scrolling was too wonky for my nerves.
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.
