So a bit under 3 years ago, I made my infamous Wayland rant post that is likely the most read post on this blog by miles. I should really actually write about music again one of these days, but that’s a topic for another time. The language was perhaps a bit inflammatory, but I felt the criticisms I made at the time were fair. It was primarily born out some frustrations I had with the entire ecosystem, and it was not like I was the only sole voice. There are other people out there you can find that encountered their own unique Wayland problems and wrote about it.
With that post, I probably cast myself as some anti-Wayland guy which is my own doing, but I promise you that is not the case. You can check my mpv commits, and it’s businesses as usual. Lots of Wayland fixes, features, and all that good stuff. Quite some time has passed since then, and it is really overdue look at the situation again with all the new developments in mind. To be frank, my original post is very outdated and it is not fair to leave it up in its current state without acknowledging the work that has been done. So in comparison to 3 years ago, I have a much more positive outlook now.
I knew dudemanguy would eventually make a post like this. I use the distro(Artix Linux) he’s a maintainer on Artix, and he’s a solid dude that is always willing to help and gives solid help.
I have both riverwm and bspwm along with Wayland and X on my system and honestly have stuck on X because getting my workflow exactly the same on Wayland has been a technical hurdle of learning Zig (riverwm is written in Zig), and so far, with the exception of the occasional race condition, X just works.
I want to convert to Wayland, and will probably get around to making my own custom scripts in zig for working with riverwm. But until then, X/bspwm is where I live.