cardboard VS sway

The article at the link you posted is about the Cardboard WM.

Shoutout for Cardboard, an awesome Wayland compositor and a rare example of Scrolling Tiling window management.

https://gitlab.com/cardboardwm/cardboard

You have cardboard which is a freestanding wm based on the functionality of the old paperwm plugin for gnome: https://gitlab.com/cardboardwm/cardboard

Er, on my laptop? It might be more precise to say that I can't find any way to make it use anything else; manpages give me nothing, grepping for "layout" in the source tree gives me nothing (relevant; window layouts show up), and there's an open issue (https://gitlab.com/cardboardwm/cardboard/-/issues/30) asking for it, all of which makes me conclude that it doesn't appear to support doing anything but QWERTY. That said, I said "AFAICT" for a reason; if you can prove me wrong I'll be quite grateful (because, seriously, I would like to use this thing).

They can’t be disabled, but I’ve opened a bug about it: https://gitlab.com/cardboardwm/cardboard/-/issues/27

Would it be possible to use the 'layout generator' functionality to create scrolling workspaces in the style of PaperWM or cardboard? Where rather than tiling the traditional way into the space available on the monitor, windows are tiled next to each other in columns on an essentially infinitely wide workspace and scrolled to bring the focused window onto the monitor.

PaperWM is the original inspiration, but then I acted on the suggestion of one of the developers of cardboard and made a plugin for Wayfire.

Cardboard is hosted on Gitlab at https://gitlab.com/cardboardwm/cardboard

This is partially why i use tools like i3 (/ sway). i like the tool; it works extremely well for me; the design has stayed the same for 20 years; there's no profit motive to come along and fuck everything up. it just works. it is boring in the best way possible.

I also have crashes on sway, but there’s a rough workaround now which prevents the issue totally.

I believe there’s a design issue with Firefox and GTK handling input events; some Wayland compositors have workarounds but others do not.

https://github.com/swaywm/sway/issues/7645

https://bugzilla.mozilla.org/show_bug.cgi?id=1743144

Firefox is my preferred browser and I hope we can keep its engine alive in this era of Chrome dominance.

I'm seeing this: https://github.com/swaywm/sway/wiki/Setting-Environmental-Variables but I haven't figured out how to make GDM do it, and I was wondering if there was a super simple "HEY SWAY READ MY .PROFILE" thing I could do.

So I searched around and found the following bug report where this problem and a possible solution was borough up: https://github.com/swaywm/sway/issues/2966 , which was then immediately closed again.

I've been using Sway since late 2019. I like the workflow of a WM. I honestly find it hard to go back to a DE, I like having a minimalistic desktop.

Sway is fast, minimal, and flexible. Their recommended tools/addons are worth a look: https://github.com/swaywm/sway/wiki/Useful-add-ons-for-sway

From that list I use greetd + tuigreet as my login manager, sway-launcher-desktop for FZF-powered app launching, and wob for lightweight brightness and volume display (send '50' to the wob socket and it'll show 50%; it doesn't get simpler).