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've probed a few tiling wms: dwm: never ending tinkering, a lot of frustration and despair with incombatible patches. i3: manual tiling is not for me. spectrewm: nice, but too less features. xmonad: nice, but Haskell. Awesome: at first it was not my favourite, but it comes with most of the features I need. Missing features can be added in a short time (awesome is build from C and Lua, awesome's plugins are pretty simple lua scripts). Awesome is full operable via the mouse or the keyboard - awesome is able to act as a stacking window manager; a very handy feature, when coming from a stacking window manager (I've used icewm for twenty years). Summary: a very good tool to form a work environment that is adapted to your personal workflow.

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.

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

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.

@cyclohexane for me it was and always will be bspwm. Once I had it configured it was the coziest of cozies.

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.