Linux

I used StumpWM for many years. It was great for most of my workflow and, being written in Common Lisp, you can recompile parts of it while it's running (I didn't do this often but it was a cool feature).

Sway with autotiling and a few nifty scripts (launch or focus and such) and Waybar. The combination of having scratchpads, sensible autotiling along with titlebars and the wonderful world of wayland is supreme.

@cyclohexane Good old i3, easy to setup and use, though the default config of i3 is really bad.

I've been very happy with hyprland since it's the only Wayland TWM that allows a great experience with nvidia.

switched to hyperland from i3. Both work well in the end.

herbstluftwm - because it just works and does not try to think for me;

The configuration is a shell script using herbstclient to talk to the wm process, that's a plus for me, too.

I've tried AwesomeWM but couldn't get anything going with it really.

I then moved on to Material Shell (yes that's a Gnome Extension) and it brought enough to really make me want to dig in more.

Now I'm slowly working on a Sway configuration on my Fedora 38 machine. Can't work in it yet, but unlike my attempt at AwesomeWM...I'm actually making progress on getting things setup. My 4 monitors were configured fairly easily, but now I need to figure out why dmenu isn't working to launch applications. Could be on my end since I'm using a Moonlander keyboard with a custom DVORAK profile.

I used DWM for a year or so (still do use it on my librebooted 2008 T400 gentoo thinkpad just to stay below 100MiB of memory after boot for the lols) and recently switched to sway.

My primary reason for sway was it being relatively simple and to try out wayland (which works with minor bugs in xwayland). Initial configuration took me about 1h and i wrote a small program in rust to populate the title-bar. Works like a charm and i like my stuff to be simple so i don't think i will look into different TWMs.

I'm using sway on top of fedora. I heard positive things with i3, but I wanted to try something that was native wayland.

I use i3, but to say that I like it is a bit overstated. It's fine, does what I expect the very basic of a tiling window manager to do. I used Nimdow for a while and it's pretty good, the default bar is way better than i3 (supports ANSI colour coding, mouse presses, etc.), but I could never quite get to grips with the tiling algorithm.

I'm working on my own WM though, it's not tiling per-se, I choose to call in non-overlapping and I'm trying to solve my gripes with i3. Basically windows should not be forcefully expanded if they don't want to. Try open galculator under i3 and watch the horror. And when expanded the size should be split based on their initial sizes. So if I have Firefox open and want to do something in a quick terminal window the terminal won't get 1/2 of the screen. Firefox wanted more space than the terminal initially, so the terminal gets to take up a smaller share of the space.