river-classic: river 0.3.x forever
6 points by miro
6 points by miro
to give some background - river is dropping its window manager (which has been forked into river-classic) shifting focus to river-window-management-v1 protocol and while I like the idea of having an easy-to-use compositor that is not tied to a window manager I find this decision to be rather disappointing.
There are already seven new window managers utilizing the protocol. Don't get me wrong I think it's great, but user space would greatly benefit from some stability (especially on the Wayland side) rather than having another project forked and reworked.
Agreed. I’m on river classic and when rwm dropped I didn’t know what to do since it doesn’t come with its own wm impl.
It’s also confusing because wlroots also plays a part here. So it’s Wayland -> wlroots -> rwm -> wm
Now when debugging there’s a bunch of layers to understand and how they interface with each other.
rwm should have been a completely new project and left river as-is. I’m sure there’s a valid reason but it’s gonna confuse a lot of users.
I’m curious, where’s this list of WMs ontop of rwm?
rwm should have been a completely new project and left river as-is.
agreed, this way it just adds another hoop on top of the insane web of dependencies you mentioned.
I’m curious, where’s this list of WMs ontop of rwm?
https://codeberg.org/river/wiki/src/branch/main/pages/wm-list.md
I skimmed through some of them and they look interesting don't get me wrong, but I wouldn't trust any of them to daily drive on my machine.
off-topic, but dwl is unmaintained for ~5 months now so that just adds to the pile of abandoned projects.
Sigh, I wonder if river will get maintained over the years. It does exactly what I need it to so I don't need feature development, maybe that's fine?
I guess I could try niri or go back to sway ...