i've tried switching from x11/i3 to wayland/sway. so far, it's been going okay, i suppose. it wasn't a seamless transition, but it went smoothly i'd say.
i wanted to switch over, simply because i wanted to try out wayland, since i've been using x11 for like a decade lol. wayland basically has always been in a "soon + 2 weeks lmfao" state ever since i started using linux so it's been nice to see it working so nicely. but it's not like i don't have my issues with it.
a lot of things i used to use on xorg simply don't work on wayland (scrot, polybar, etc), and i've had to find alternatives for them. switching to grimshot and waybar has been surprisingly not that big of a deal.
some things were broken initially. minecraft didn't function at first with the tiled mode. it rendered at the default resolution, with pure white around everything else. with the use of an environment variable, that has been fixed.
wayland, by nature, has no screen tearing. that's great for the desktop, but for games, that fucking sucks. i can just FEEL the fucking input lag from the forced vsync on everything. sway 1.10 will allow me to enable tearing, but it's still on rc4. on 1.9, which is what i'm using, there's vsync up the wazoo and it's painful for me, who was used to using i3 without a compositor at all.
thankfully, that's going to be fixed (i think???) reasonably soon.
most things have support for wayland now, and if they don't, xwayland works fine enough. i've had trouble with getting obs to work but maybe that's because i'm retarded. screen sharing seems like a pain in the ass on wayland
overall i'd say that sway and wayland is okay enough for me to use on a daily basis. i've got some minor issues with it, but other than that it works well enough for me. rightt now i'll hop on over to i3 if i want lagless gayming, but for everything else sway just werks. once sway 1.10 gets released with the tearing control protocol i'll switch over permanently to sway.
----
written on 2024-10-25