kwin-tiling VS sway

KWin used to have no tiling capabilities at all and people came up with lots of add-on scripts like kwin-tiling, Grid-Tiling-KWin, Krohnkite, Bismuth and so on. This gave users tiling, but it was always a bit hackish, getting KWin to do something it wasn't designed to do.

I said I was using kwin-tiling-script, and yes, it does have that—I use[d] it all the time (it's called "Grid" layout)

If you're referring to kwin-tiling the author has archived that as of end of 2022 and it's unmaintained. It's not really anything KDE did on purpose except to do the usual updates and that's broken an unmaintained project.

I use kwin tiling

If you are ready to sacrifice gaps (and some other advanced features like taking away title bar from tiled windows) and run multi monitor, then I would suggest kwin-tiling. It has no settings, but out of the box with changing hotkeys similar to i3wm you can get great tiling experience (it even supports moving window from monitor to monitor using meta+shift+hjkl if it hits on the border)

The last DE I used before jumping to bspwm was KDE with kwin-tiling and one of the features I miss is the ability to change "on the fly" the opacity of a given window with keyboard shortcuts.

I like KWin-Tiling-Script (https://github.com/kwin-scripts/kwin-tiling), but Bismuth has better desktop integration and is more popular.

Before making the jump to a tiling WM , I think you should use a tiling KWin script for KDE. It will help you get used to a tiling WM but still have the familiarity of KDE. https://github.com/kwin-scripts/kwin-tiling is a good one that I use.

Indeed. This has served me well: https://github.com/kwin-scripts/kwin-tiling

Hi, I'm using "Tiling from Faho", it has also i3 mod. For additional info visit kwin-tiling (for enabling settings buttons see last section Troubleshooting).

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).