Sway for going on 2 years I think. I do recommend it, and Wayland/tiling wms in general.
I use my own fork that uses bspwm-style “long-side split by default,” and a nearly transparent under-the-hood container-squashing refactor that prevents this behavior from causing the tree to become bloated with invisible nodes and start to lag horribly. The fix won’t be accepted in Sway since it’s the bug is faithfully reproduced from i3, and I haven’t had time to rewrite it for i3. But if you use something like sway-autotiling, you’ve probably noticed the issue.
Sway for going on 2 years I think. I do recommend it, and Wayland/tiling wms in general.
I use my own fork that uses bspwm-style “long-side split by default,” and a nearly transparent under-the-hood container-squashing refactor that prevents this behavior from causing the tree to become bloated with invisible nodes and start to lag horribly. The fix won’t be accepted in Sway since it’s the bug is faithfully reproduced from i3, and I haven’t had time to rewrite it for i3. But if you use something like sway-autotiling, you’ve probably noticed the issue.