wayfire VS river

Unusable until moving your mouse to the edges of the screen and clicking makes it hit the scrollbar, or the exit button. Right now it initiates a resize.

Illustrated example from a different compositor https://github.com/WayfireWM/wayfire/issues/570

It's the only DE I'm excited about it so I hope they fix that. Very very promising and the best part is that it made the GNOME people mad.

GNOME: "Sorry I don't see the use case for that, PR closed. Make your own project. "

One of the developers just responded on the github issue referecing this thread.

"After a bit of discussion on HackerNews, I got a bit better understanding of the actual problem. People don't want to just configure the keys according to a particular layout - the actual 'issue' here is that they expect the key binding changes together with the layout. Unfortunately, the 0.8.0 changes didn't make this possible to implement as a plugin.

I would reconsider adding this as an option if there are enough interested people. React with a thumbs up to this comment if you are interested in having this option (though the defaults will certainly remain as they are now). Please, react only if you actually use Wayfire or would use it if it had this feature :)"

https://github.com/WayfireWM/wayfire/issues/1601#issuecommen...

I have been on Wayfire for over a year now, and I can't possibly praise it enough. It's entirely modular, so you can make it look and behave exactly as you want. It does tiling, it does Compiz-style wobbly windows and 3D desktop cubes, configurable rules and hotkeys, everything. It's stable and handles gaming flawlessly.

Your impression of Wayland is going to be very much determined by the quality of the compositor implementing it, and I've found Wayfire to be the best, by far - but oddly, also the one least talked about. Everybody's paying attention to stuff like Hyprland, Sway and Mutter - you're barking up the wrong tree there. Wayfire is fantastic, has most of the bells and whistles Compiz on X11 has, and is as pretty or as functional as you want it to be.

- VR support

I thought so too not long ago, but Wayland compositors needed some time to mature, and some of them are getting pretty damn good. Ever since I discovered Wayfire I'm a total believer, it's better than any X window management solution I've used. Much lighter too.

might be a small window when wayfire releases a version, before master identfies as the next release number. (see: https://github.com/WayfireWM/wayfire/blob/master/meson.build )

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