I use it as my daily driver. I used Sway for a very long time, tried Hyprland for a bit and am now running niri as my daily driver. Sway and niri are wlroots based, Hyprland at some point rolled its own because they didn't want to wait for wlroots protocol extensions. Sometimes I have to switch to Gnome to do screen sharing.

2026 and you will still run into plenty of issues with random behaviour, especially if you run anything based on wlroots. Wine apps will randomly have pointer location issues if you run multiple displays. Crashes, video sharing issues with random apps, 10 bit issues. Maybe in 2027 we'll finally make it. But I feel like these 20 years of development could have been better spent on something that doesn't end up with 4 or more implementations.

▲

myaccountonhn 3 days ago | parent | next [-]

There also isn't nearly as much choice for wms. My favorite WM is cwm, but the closest alternative on Wayland is Hikari which is abandoned.

I noticed it's far far more work to build a wm for Wayland than it is for Xorg.

	▲	rjzzleep 3 days ago \| parent [-]
		Every single one of them has to fix the same set of bugs in different ways even if they share a wm library like wlroots. So unless you manage to get a critical mass on your wm, there is no way you can maintain it on your own. If I believed in conspiracy theories, I would have said that Redhat designed it to make sure they can control the ecosystem, but I think it's just over designed in all the wrong ways.

▲

abhinavk 4 days ago | parent | prev [-]

niri is based on smithay which is also used by COSMIC.

	▲	rjzzleep 4 days ago \| parent [-]
		I used rust for my sleep daemon, but personally I think rust is a suboptimal language for efficiently writing wayland code.