waymonad VS river

I am personally waiting for Waymonad. https://github.com/waymonad/waymonad

It takes time, but the teams behind wlroots etc are doing good work to make sure that wms managed by smaller teams can exist. There are even clones for your specific wm on wayland. See https://github.com/waymonad/waymonad

In addition, there was the last commit in 2019. Thus, it can be assumed that the project is dead and therefore nothing will change on the current state. And according to https://github.com/waymonad/waymonad/issues/44, there are probably not enough people who would actively participate in a fork.

Ideally xmonad would be ported/xmonad devs would be working on waymonad, but I doubt it will happen. Waymonad seems to be abandoned.

Nice to see Qtile on Wayland. But I'm personally waiting for xmonad on Wayland.

https://github.com/waymonad/waymonad

I wouldn't count on it, as Waymonad has not seen active development since 2019 and the Haskell bindings to wlroots have not been updated since 2019 as well. There is a fork, but it has not been active since September 2021. Also, it was based on wlroots, not sway.

That's what the XMonad fans are using: https://github.com/waymonad/waymonad lets you write your Wayland compositor in Haskell, is analogy to the way XMonad lets you write your X window manager in Haskell.

Unfortunately it was abandoned https://github.com/waymonad/waymonad/issues/44

regarding keeping an interest, waymonad has been dead for something like two and a half years but according to startrack it's still getting people giving him stars so i don't think you should worry about it.

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