I'll second this. It was well worth the couple of evenings switching to i3 and getting up and running. Besides no maintenance work, there are three main reasons

I'll second this. It was well worth the couple of evenings switching to i3 and getting up and running. Besides no maintenance work, there are three main reasons for me: 1) Most of the default config works well out-of-the-box, and you can tweak away things to your liking. Documentation is short and to-the-point. 2) It's possible to start processes and put windows where they belong at startup, using an extra layout manager. You later can tweak the setup by manual keystrokes according to extra needs and there's always extra workspaces you can move to. 3) By splitting parent container from child container, you can keep a fractal hierarchy of containers for putting/moving windows in. This can be managed by keystrokes according to need, and makes it easy to tab/stack/split windows or change part of workspace layout manually, without windows unexpectedly jumping around too much. Most guides fail to show the advantages of this, and is something most tiling WMs lack or implement poorly. Again you get this by default.