Seems like a deal breaker.

I swap workspaces very often with my tripple monitor xmonad setup.

I have nothing but respect for vaxerski. He's 100% dedicated to the project and is incredibly prolific. But I feel like they need a better release strategy for those who prioritize stability over shiny new thing.

Paper (for GNOME shell) introduced a new tiling window manager paradigm: scrolling workspaces. New windows are placed to the right and build up in a stack. You push and pop from this stack as you enter and exit subtasks. For example, you might be editing code and want to open a PDF to find some datasheet values, then open a repl to do some calculations, then close both those windows and put the result into your code. The new windows grow out to the right, then you close them to scroll back left to the code.

While tools like papersway managed to hack a paper like experience on top of sway, niri implements it from the ground up into a window manager that is as light as sway but designed with scrolling workspaces as a first class citizen. For example, it has an overview mode for zooming out and seeing many workspaces at once. Given that the raison d’etre of the paper/scrolling paradigm is to be able to handle large numbers of windows, once you’ve used niri+overview it is very hard to go back to sway and live without it.

It is very nice! It’s also not really an improvement if you live in two windows all day long (80% if my time all I have open is a browser and my code) but as soon as you start having to context switch in and out of other tasks on multiple tracks (mortgage application, CAD design, proposal doc editing, email follow-ups, procrastinating on HN!) having paper like scrolling stacks is a huge boon.

Though I have the eye candy stuff cranked way down, doesn't really add too much for me.

It's pretty solid but I dislike that I had to install many additional things for everything to work smoothly. I think some "more sensible defaults" really wouldn't hurt.

I mean just go to https://wiki.hypr.land/ and take a look at the "Hypr Ecosystem" navigation entry. Really? I need to install and learn about ~15 additional hypr* binaries to use this as intended?

One footgun is podman stop kills the display manager unless you launch terminal in its own subprocess.

> NVIDIA GPUs are often not usable out-of-the-box, follow the Nvidia page after installing Hyprland if you plan to use one. Blame NVIDIA for this.

> Debian and Ubuntu’s Hyprland is extremely outdated. I do not recommend using the packaged versions at all. Build the entire stack manually instead.

Any good alternative that works on my setup?

But, until there is a Fluxbox clone on Wayland that can use ~/.fluxbox without any configuration changes, I will stick to X11.

As a second choice I would accept a cwm clone that can use the same config file as cwm(1).

It's already quite stable even though it's an alpha version, possibly thanks to being implemented in Rust. I've been using it daily on my personal laptop since its release in April. No big problems, some missing features and tweakability though.

The guy that writes it/maintains it is a piece of shit though. The last thing the Linux community needs is more bigotry and anime crap.