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.

Interesting to see, you’d think this would be the #1 safeguard you add. It’s even the main trope of AI stories like the paperclip machine that if a poorly incentivised AI goes wild it would do stuff like this.

Nim