PaperWM VS sway

But with auto-tiling you need to place windows according to a pre-set configuration, it needs to fit whatever layout you want to go for and it needs to be able to resize the window without breaking the content. This works pretty well for libadwaita apps, but a lot of webapps seem to assume a certain minimum window size. Another issue is how to handle modal dialogues, where paperwm for example sets an override to ensure they're not attached to the main window. Should the settings window then be treated as a separate window and tiled, or should it be left floating above all others?

I like Gnome's simplicity, agree with most of its deviations from the tired old Windowsy desktop status quo, and am very happy to depend on all its great integration work. I can't quite live with the simplistic window management, but extensions cover that (as they do much else). With Fedora + Gnome + PaperWM, I'm quite at peace with the current linux desktop situation.

Still I'm looking forward for something like PaperWM to be possible in KDE - or even to write it by myself

I have noticed in one of your comments in this thread that you are looking for novel ideas of the UI look. As others commenters stated, you might be interested in tiling window managers like i3 [0] or sway [1]. They are truly a gem for productivity and sometimes for an eye [2].

However, I love the concept of scrollable window manager like PaperWM [3] is. When I had a smaller screen (24" 16:9) I was complaining a lot on unused space on my screen. With PaperWM I was finally happy with its dimensions, because I could have huge IDE on the left and small part of terminal displayed on the right. That way I knew if something was printed to terminal, while my editor took 80% of the screen.

[0]: https://i3wm.org/

[1]: https://swaywm.org/

[2]: https://www.reddit.com/r/unixporn/

[3]: https://github.com/paperwm/PaperWM

If you want something really different, give PaperWM a shot.

You may want to try PaperWM (GNOME extension) https://github.com/paperwm/PaperWM

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