river VS Hyprland

https://github.com/riverwm/river#future-plans

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

Some context for anyone unfamiliar with the linux desktop space:

Hyprland is a "wayland compositor" (roughly analogous to an X Window Manager) that is under active community development: https://hypr.land

Wayland is considered the future of the linux desktop and is what projects like Valve's SteamDeck are using: https://github.com/ValveSoftware/gamescope

It's known that Hyprland Premium is going to include a bunch of pre-made dotfiles including a Quickshell bar config, if you want to see the current top-tier rice: https://quickshell.outfoxxed.me/

> If you’re someone who grew up on Macs there’s almost nothing in the Linux desktop space that tries to replicate that set of patterns… it’s all Win9X-type taskbar setups, mobile-type setups (GNOME, Pantheon), old niche *nix setups (e.g. WindowMaker), and of course minimal tiling WMs. There’s no clones of Mac OS of any flavor.

Have you seen [Hyprland](https://hyprland.org)?

If you go to the homepage: https://hyprland.org/

It says "Tiling Compositor" as its first words. That's what it is.

It's not a "window manager" since that's an X11 term, and this is a Wayland Compositor, not an X11 Window Manager.

I feel like the landing page explains very clearly what it is for the target audience, which is someone who uses wayland and knows what a tiling compositor is.

and yet hyprland uses a CoC?

https://github.com/hyprwm/Hyprland/blob/main/CODE_OF_CONDUCT...

I joined the hyprland discord after seeing many reports of hyprland having a "toxic" community to verify the claims myself, I must say I'm disappointed. I expected to see some real raunchy stuff, instead it's quite literally one of the most trans-positive and otherwise politically milquetoast servers I'm in.

The initial rules post you have to agree to before gaining access to the server has hundreds of reactions of various trans flag emotes too.[0]

What's the problem here? The whole drama seems like virtue-signalling politically-correct FOSS devs attacking other politically-correct FOSS devs.

[0] https://imgur.com/a/HKrFtbZ

I've been wanting to try http://hyprland.org/, but since plasma gets me far enough and provides a working taskbar (wifi, sound, bluetooth, mount, clipboard) and virtual desktops on which I end up opening just firefox and emacs I haven't really given it a chance.

Hyprland builds using a pinned commit of wlroots instead of a tagged release because wlroots release schedule is too slow for Hyprland's development [0]

This turns into a problem for maintainers because many distributions refuse to ship non tagged versions of software

Hyprland used to depend on wlroots-git, but when it made the switch to use specific pinned commits a lot more distributions started to package it [1], but some still refuse to do so such as Debian.

[0] https://github.com/hyprwm/hyprland/issues/302#issuecomment-1...

[1] https://gitlab.alpinelinux.org/alpine/aports/-/merge_request...