i3 and sway

i3 all the way

XMonad. Been using it for almost a decade, and very powerful. I3 I hear is also good.

i3 until the day I die

Edit: Why? Because I love how easy it is to get working, it's a nice balance between features and simplicity for me, and IPC features are great for some QoL plugins. Its configuration file format is simple enough, I like lua with wezterm and neovim but I don't really see the point with a WM, I just need to see my windows when I want, the way I want, and to switch to others.

i3 gang rise up!

I've only tried i3 and it just works, so I stuck with it. After learning the hotkeys it never seems to get in the way (at least for my usage). Riced it a bit. Then some polybar sparkled in there. A wallpaper. What more can a guy want?

i3 is what I've been using the past few years. I've tried others, but I always end back up with i3 as I've found nothing else to be as simple and efficient for my workflow, with 12 workspaces across 2 monitors.

I’ve been using i3. Nothing super advanced but the config is easy and being able to reload in place is nice

I usually use tiling add-ons for Gnome or KDE. So pop-shell or bismuth.

Sway, but single window capture and the animations make hyprland very tempting...

My heart still belongs to enlightenment/e17 but I've been using i3 for the past few years, and then hyprland for the last 4 months or so. It's working out well.

I tried i3 back in 2019 and I've been using it ever since on my desktop.

Today I use Plasma, but if I need a tiling wm I use awesome. It's so great and customizable. If you're fine with Lua, is easy to config.

PaperVM. Works under gnome and has everything i need

HYPRLAND !

Starting with i3 as my first, i tried a bunch of different ones. Xmonad and Qtile were the ones i liked the most but Qtile was buggy and Xmonad while working was super confusing to configure with haskell.

Also tried AwesomeWM, it felt a bit buggy to me in terms of window handling and DWM was just too complicated to patch and even with patches it was too basic

Ended up going back to i3, and then moved over to Sway.

i3 is the one I keep coming back to

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.

Recently I have been using river. It's extremely easy to configure via a shell script, and it's very fast and stable. It's another dwm clone

DWM due to it's suckless nature

Currently, I am using DWL and it is pretty nice. After moving to Wayland, I tried to use Sway for a while, but it does not really fit into my workflow well. But to be honest, even DWL is missing some things I want, and I am not really a fan of that it is written and configured in C. I am planning on trying to write my own tiling window manager in Rust when I have some time.

Not sure if this counts as a tiling window manager, but I spend most of my time in emacs in full screen mode. I can create, delete, resize, and swap my windows.

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

EXWM. I am a longtime Emacs user so merging the concepts of Emacs buffers and X windows is a huge benefit. Only one set of keybindings to worry about, all of my Emacs window management stuff works for X windows too. One less external dependency to worry about too. In a new environment (like when starting a new job etc) as long as I have my Emacs config I am good to go.

Pop!_OS 20.04 LTS... I love how it combines tiling and stacking. Sure I could use workspaces instead of stacks, but with stacks... I can use both!

I've also used EXWM and am going to give it another whirl after I upgrade to emacs 28 with native comp

I've been using dwm for a while now, I have a custom arch PKGBUILD to patch it the way I need and I'm generally satisfied with it.

the big downside is that you do need basic knowledge of C to actually configure it and quite a willingness to play around when applying patches, if you go the dwm route make sure that you're applying your patches via some script so you can easily take patches out or reorder them without having to rebuild everything from scratch, there's also a version that you can enable/disable patches and rebuild; but I haven't tried that yet.

DWM

I started with for a bit awm, however i am giving qtile a try since im learning how to code python so good practice.

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

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.