Linux

PaperVM. Works under gnome and has everything i need

bspwm. Initially I found the way it split up bspwm from bspc intriguing. Also messing around with the configuration is less of a pain in the ass than dwm was which I used for some years previous to bspwm. At this point there's a lot of inertia as I've been using it for years, but it seems like wayland is going to be the thing moving forward so I should probably be thinking about a compatible replacement.

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

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

AwesomeWM because nice defaults and you can configure it with Lua like neovim but I want to try hyprland in the future

Currently using sway, but mostly for the lack of good Auto tilers on Wayland

Normally, I use bspwm, but I recently was forced to switch to wayland, so I've been using sway, it's not perfect, but I'll probably get used to it, and I haven't fully configured it yet.

awesomewm and only awesomewn for the level of freedom in customization it grants.

i3wm, tho I do wanna move to wayland.

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

i3 just works in my opinion, and I can change stuff how I like it. It's simple and has loads of users, so guides are easy to come by.