I'm gonna throw my hat in the ring for Xmonad, but I personally love auto-tiling, CLI apps, and hate desktop icons so it's a bit more retro-minimalist than pure retro.
I would use stumpwm because I prefer lisp over haskell for config but it doesn't support auto-tiling yet q.q
Absolutely! Though I'll warn you, if you're on a multi-monitor setup the configuration is a little wacky unlike the other tiling wm's that handle it gracefully like i3 et al. Just let me know if you need any code for that and I can send you my config files 😄
Also, if you happen to be using Guix, you have to install some extra deps to build from the xmonad.hs file, even though "xmonad" will "work" without them. So just be careful there too as I hit both of these walls face first about a year (or two?) ago and it was...unpleasant 😂
@johnabs@qoto.org @stdevel@chaos.social auto tiling has been supported for a long while, I have half of my groups use it
https://github.com/stumpwm/stumpwm/pull/851
@iska @stdevel Hmmm. I may need to check this out again!
I've made the transition from i3 to dwm to xmonad, but if this can get me to a dwm/i3 experience with as much stability as (or preferably more than) xmonad, I'll probably switch.
Re-building xmonad on guix is a nightmare, especially when someone changes an abstraction and I have to completely rewrite my config 😭
Does it handle multiple monitors well, and switching between monitors? And can you have multiple workspaces per monitor? Do you recommend anything from stumpwm-contrib?
@johnabs@qoto.org
@stdevel@chaos.social I don't have multiple monitors, but my setup does use a bunch of contrib packages: kbd-layouts, gaps, notify, mem, desktop-entry and ttf-fonts
for desktop entry and gaps I had to make my own patches for them to work 
and ttf can slowdown when there's lots of text (i.e exec), so not a good idea for a laptop
