4 ms·
You’d think that Microsoft and Github would have a monopoly on this given their personal contributions to Git, ownership of Visual Studio Code, and ownership of
by CSSer 4y ago
You’d think that Microsoft and Github would have a monopoly on this given their personal contributions to Git, ownership of Visual Studio Code, and ownership of the largest Git hosting PaaS.
Don’t get me wrong, VS Code and Github are both okay. I use them both and drop into the integrated terminal for situations where my muscle memory is faster or the workflow is going to be more complex. I also find that setting VS Code to my default editor for Git makes this pretty seamless. Anyway, I find it interesting that there doesn’t seem to be a big focus on the sort of features the author mentioned in VS Code.
Now that I think of it, this is also one of those few circumstances where I don’t need or want the tool to be modular. VCS are such a fixture today that I just expect this to be built into the IDE’s GUI. A separate app, even with perfect workflows, may be just as much of a bother as a terminal. After all, what’s stopping me from writing a handful of clever aliases?
- heywhatupboys 4y agoare you unironically wishing MS would EEE git? lol
- DangitBobby 4y agoThe only passable git GUI IMO is the one built into Jetbrains IDEs. VSCode makes only the very most basic workflows simpler (doing a commit) so I use that as well on the rare occasion I'm using VSCode. For every other git GUI, I'd rather just stick to CLI.