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 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 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.
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.
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.
When it is ready and passes black screen or can use hardware acceleration without crashing compositor, I’ll use wayland
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.
@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.
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.
When some crappy vendors (ahem, Zoom) bother to get screen sharing working on Wayland.
Until then I’m stuck on xorg at work, but it’s Wayland all the way at home… not by explicit choice, just the distro default.
When XFCE supports it.
I’ll adopt it when it becomes Linux Mint’s default
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 switched my laptop to Wayland about three years ago. AMD graphics, normal DPI 60Hz screen, doesn’t really do more than run a web browser.
My gaming desktop needed more of those troublesome edge cases hammered out - freesync in xwayland, app DPI scaling in xwayland, etc. I only switched it last year.
When? Since Ubuntu made it the default for non Nvidia PCs
I used Wayland for a couple years on AMD hardware and it was fine; I didn’t really have any issues. Since acquiring a laptop with an Nvidia card as a gift about a year agi (it was a hand-me-down), I switched to X11 because it is still more stable for Nvidia. I will be switching back to Wayland (with Nvidia) when Fedora 40 releases. Hopefully the support for explicit sync patch will be available by that time, but if not I won’t be heavily affected, as I am not playing games currently. I expect that patch to fix the black frame insertion during VRR that people have been complaining about, at which point Nvidia will be viable (for me) on Wayland.
I’ve been on the Wayland train for quite some time now, it’s only really had issues with Nvidia because Nvidia refuses to adapt their graphics driver for it. We have to rely on the Wayland and XWayland projects to fix the incompatibilities that Nvidia is too lazy to fix themselves (like not supporting implicit sync). Luckily AMD is on top of things and has worked very well with Wayland for years now, so those with AMD hardware are better off.
EDIT: Here’s a link to a Lemmy post about the explicit sync patch. Looks like Nvidia drivers plan to support it in the May 15th patch, so about a month after Fedora 40 releases.
i’ll probably jump the next time i change window managers or distros… i havent a reason to currently
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.
