> It's probably laziness. Is that such a bad thing though? Yes. > I think its ok to expect tooling to be easy so we can spend our times on actually writing co

> It's probably laziness. Is that such a bad thing though? Yes. > I think its ok to expect tooling to be easy so we can spend our times on actually writing code. I have never seen someone use a git GUI alternative as quickly and effectively as a competent CLI user. Especially if you're dealing with anything of reasonable complexity, but still, even for simple stuff. I can hit F1 for my quake-like terminal and type out `git add . && git commit -m 'Adds [...]'`, or a `git stash`, etc. faster than someone can reach over to the mouse and even open the GUI (let alone actually committing). That's not to say that I don't use Sublime Merge but it's only for complex visualization situations of weird branching etc. But... it's worth noting that most of the time I can get that hammered out on my GitLab instance. So, if you're looking for efficiency and want to "spend time actually writing code" I attest your argument that a GUI would speed anything up only if you refuse to learn the CLI. > To me it's the same thing as expecting auto completion and line by line debugging from our IDEs I work in Sublime all day long and actually actively turn features like this off because they slow me down. Also this is not to say I don't often jump into Intellij for heavier IDE stuff (step-through debugging) but that's like 1-2 times a week max. Otherwise, get out of my way and just let me get the code onto the page, I know 100% what I'm doing/writing and my docs are immaculate and accurate. --- Overall we probably work in very different ways, with very different development philosophies - which is 100% fine =)