river VS cagebreak

More info on the wiki https://github.com/riverwm/river/wiki

Here is the related github issue

If you can get past some minor wayland related annoyances, river is pretty easy imo, you can write a config in whatever format you want, it just needs to be an executable file, the most common type is a shell script. The actual configuration happens by calling the riverctl program from the file, which from what I've heard is a similar method compared to bspwm.

Coming from awesome you may find river more to your liking than sway.

River crashed everytime I closed Chromium. The developer fixed it in 5 minutes :)

I've written a plugin that implements the river-layout-v3 wayland protocol in Hyprland. This means you can run something like rivertile, river-luatile, rivercarro or kile as a layout provider.

Author here. And yeah, as of 0.6.0 it supports master stack - I just called it stack main. I was in fact inspired by river: https://github.com/riverwm/river. River is really promising but is still in very early development. Sway on the other hand has been around for a long time and I, for now, prefer that stability.

In my very specific case, I'd probably start by taking a look at how animations were previously implemented in river, and then I'd pay careful attention to that transform matrix at the end. I'm not super crazy about the implementation using timers to drive it (versus interpolating where the transform should be across a deadline), but I guess they were going for smoothness.

riverwm wayland compositor

There's also a Wayland WM directly inspired by ratpoison! https://github.com/project-repo/cagebreak

That's true for a lot of libraries, you have to maintain the code, I would treat that as a fact of life, It might be worth noting there are some projects designed to provide a high level abstraction over wlroots which might be different: cage -> used by cagebreak phoc -> used by phosh and wayfire -> used by swayfire.

cagebreak as far as i can tell is a one man project (it uses cage to provide a high level abstraction over wlroots).

I also remembered cagebreak (wayland window manager). it uses cage (which is defined as a "wayland kiosk" but might also be used as a high level abstraction over wlroots).

Anyway, like you I also wanted to see how far I could go on Wayland. After trying out a number of wms I settled on cagebreak which is modeled on ratpoison. It's still in early development but worked well enough for me to give it a semi daily driver status. It works really well with emacs too, without the single-thread issue. I went for a pure Wayland experience (without XWayland as well), so I couldn't some apps I normally use - but I was able to create something quite close to my xorg setup.

There's cagebreak, wich is inspired by ratpoison. It's different yo hlwm, but it has the same concept of containers, but every container only have the "max" layout