I guess tiling window managers should be considered more of a specialized niche tool, and in that it is commendable that i3 does such a good job of it. I do really admire it for being so light-weight on resources compared to a lot of the other more popular WMs. I say a niche tool because I've never really understood why someone would prefer a Window Manager that places a lot of constraints than one that lets you cont…
i3 4.18
31–40 of 188 posts
Re: i3 4.18
#32i3 ruined my life. It's an absolute delight to use, particularly when programming. However, its hard to get Linux laptops at work (Mac or Windows), and I constantly miss i3. Also, among all tiling window managers, I think its config is probably the most intuitive to mingle with. Hardly ever breaks (if ever) between upgrades, and default workflow is very intuitive and explicit. Other window managers (eg. Awesome, xmon…
The reason (at least for AwesomeWM, but DWM too) we use pre-defined layouts is because you can (and should) pass your own functions for each tag/workflow. This way you don't have to manage the layouts manually.
Once you add the custom business logic, it becomes very predictable. Plus, AwesomeWM is modular, so if you want i3 style layouts, you can just do it (https://elv13.github.io/client_tiling/dynamite.html , by me). Of course not all users want/have_the_time to optimize their workflow. Those people should probably stick with i3. AwesomeWM is all about customization/workflow_optimization, that's time consuming, but you have a good ROI.
Re: i3 4.18
#33Re: i3 4.18
#34However, could someone who used both elaborate on the differences? Would I gain anything from trying to migrate to i3 instead?
At my point of view, only the community size is the difference, but that hasn't bothered me too much as awesome for most part just simply works.
Re: i3 4.18
#35My current setup i3-wm on Manjaro, alacritty with fish is exactly what I need.
Re: i3 4.18
#36Earlier quoted context omitted.
With exception of the directional keybindings. I wonder how it came to be that the defaults are "jkl;" for the directions instead of the "hjkl" used by everything else (vi(m), less, shells, repls, etc.).
i am always surprised when people do not have noremap ; l noremap l k noremap k j noremap j h
Re: i3 4.18
#37Re: i3 4.18
#38Still no gaps support on main branch. Devs don't care about what their users want/need. Happy bspwm user here.
I wonder if people who like gaps like bezel on their screen too.
Re: i3 4.18
#39I guess tiling window managers should be considered more of a specialized niche tool, and in that it is commendable that i3 does such a good job of it. I do really admire it for being so light-weight on resources compared to a lot of the other more popular WMs. I say a niche tool because I've never really understood why someone would prefer a Window Manager that places a lot of constraints than one that lets you cont…
Yet they've been steadily adding tiling features since Win7.
Don't believe me? Grab any window in Win10 and drag to any of the corners.
Re: i3 4.18
#40I guess tiling window managers should be considered more of a specialized niche tool, and in that it is commendable that i3 does such a good job of it. I do really admire it for being so light-weight on resources compared to a lot of the other more popular WMs. I say a niche tool because I've never really understood why someone would prefer a Window Manager that places a lot of constraints than one that lets you cont…
Most of the time it's easier to keep different windows in different workspaces though. My first five workspaces are always
1. Browser
2. Browser
3. Code
4. Messaging apps (in a vertical stack)
5. Terminals
Pressing the number for the workspace where you keep the window you want is way easier on the eyes and brain then hitting alt tab and examining the pop-up panel to see how many more times you have to hit it.