Show HN: A Native Tiling Window Manager for Windows 10, Inspired by I3wm
On the subject of tiling managers (I use one since so long I don't even remember when I started using those), time for a rant...<p>I never ever understood why those who do allow gaps (i.e. some space between each window) are basically all, by default (and sometimes it's very hard to change), do add "gaps" near the monitor's borders.<p>I mean seriously: why on earth are empty pixels added between the leftmost window(s) and the left side of the monitor, between the rightmost window(s) and the right side of the monitor, between the bottommost window(s) and the bottom of the monitor?<p>This, to me, makes absolutely zero sense. And they all do that, including this one for Windows 10 (as can be seen in the screenshots).<p>Why?  Really: just why?  I want to rant and ask: what's wrong with people?  : )<p>It just makes no sense. There's not a world in which it makes sense.<p>Worse, Awesome VM calls all the gaps "useless gaps" even though it's a fact that gaps <i>between windows</i> aren't useless (especially when you're tiling terminal windows with no borders or with a 1-pixel border, where it can be hard to detect boundaries between two terminals if there's no gap).<p>But gaps near the monitor's borders are really useless: it's ok, I don't risk mistaking what's at the right of my monitor (atm a physical cup of coffee) or what's at the right of my monitor (atm a tower with three Raspberry Pi stacked) for, say, a terminal window!?<p>I hacked my tiling VM (the "Awesome VM" on Linux) to not have these really useless gaps on the borders but the assumption that they should be there are so deeply tied in the code that's it's a PITA to do.<p>"Use the source Luke" and all that but, why, just why?  And why hardcode these assumptions in the code?  Why do they all do that?<p>I just don't get it and never will.<p>Rant off : )