Linux

I'm using i3 and actively trying to move off of it to something that supports wayland. Unfortunately this has been a pretty difficult task for me. So far I've built configs for sway and hyprland. I have 6 displays and really like the per-output management style that i3, sway, and hyprland all use for workspaces. Each physical output is a container of workspaces. If you do something on an output it stays on that output.

I am however having a massive issue with steam games. They are unplayable because I have so many displays and no matter what I do xwayland won't set the XWAYLAND0 display device. It's simply missing. So I can't configure a primary display for xwayland and all the games don't respect my layout. Some games also don't respond to mouse input related to this issue.

Hyprland

Hyprland is a really polished and visually appealing tiling window manager. I'm not so used to the auto tiling it does coming from i3 but I could get used to it. Unfortunately I've built a workflow around mixing stacked and tiled containers and I think this would require extensive plugin configuration in hyprland while it's supported by default in i3/sway. Some things are weirdly difficult though like moving to the next workspace on an output. Of course you can write helper scripts to do this sort of thing too so extending it's functionality is quite easy.

Sway

Sway is i3 config compatible and that's great, but I've been having a hard time with getting it's environment set up. I use fish as my shell and that seems to create some issues when starting it from sddm. My environment, specifically my path, is not set correctly, or the way I would think it should be based on my profile. I suspect this is due to 12 years of cruft in my dotfiles which I need to clean up.

Sway also does not support "auto" adaptive_sync. It's either on or off. This is not great and pretty much every other wayland window manager and display environment supports auto of some sort which applies adaptive_sync only to full screen applications.

Sorry, that got long, but I've spent many hours over the last few days working on this.

I don't

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.

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

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

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

This is perhaps cheating, but after diving deep into the hardcore tiling mangers (ratpoison, wmii, xmonad), I grew softer and stayed in awesome for a while, but eventually I realised that since all I want from tiling anyway is the ability to quickly place two windows beside each other, I might as well go with a DM that does all the other stuff I want automatically (mounting, monitors, etc.), and since KDE is now good again, and coming along on the tiling side, that's the tiling WM I'm using.

Yes, I said I was cheating ...!

I used suckless ecosystem for 5+ years, but I wanted to use Wayland so now I'm transitioning into Sway and holymoly how fast and easy it is. So simple to configure and written in C.

I use sway because when I came back after a long break, it seemed to be the one to go with. I kind of miss awesome, though.

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

I really like dwm. It doesn't seem too popular so maybe the other ones are better but it was the first one I tried so the others feel weird to me. I like the idea behind suckless in general though.