What is better to use for git: console client or graphical one?

Question

git

Hello. Switching from SVN to GIT. The question arose about how best to use it through the console or the graphical interface? I worked with SVN through a graphical interface. believed that there was no need to waste time typing commands manually, and yes, it smacks of sadomasochism. But over time, it began to seem (most likely it is) that most developers use the console. Most of the examples on the SVK seem to be through the console. Why? Are there any clear benefits? Or maybe I'm still wrong and it's more convenient to use the graphical interface? In general, please help me make a choice.

Answer 1

Guys don't have everything, so you still have to use the console. Everyday sitting in the console for routine actions like making a brunch or looking at the log is masochism.

Answer 2

Most of the examples use the console because there is only one. And there are a lot of different graphic faces. Work as you like, but if you understand git, there is nothing to worry about in the console. And if you do not understand, then the GUI will not help.

Answer 3

Git, compared to SVN, encourages frequent commits. Therefore, check how you can make a commit faster: through the command line or a graphical utility.
If you're on Windows, then TortoiseGit might be more familiar to you after TortoiseSVN. Moreover, by default, Git command completion on the command line does not work in Windows.
If you want to get closer to the convenience of using Git on *nix systems on Windows, try posh-git . This is an extension for PowerShell.
It is more convenient and faster for me to make commits, branches and merges, push&pull and tags from the command line, and it is easier to work with history and differences in files from graphical utilities.

Answer 4

In the console it's faster, in the guis it's clearer.

Answer 5

you use together. The console will help you remember commands, use features that are not in the GUI. And the GUI will help you see the turnip, feel it, so to speak.

Answer 6

Practice has shown that the less you pull the mouse while working, the faster your performance. That is why people memorize shortcuts.
Usually programmers type extremely quickly, and the console still has autocomplete and aliases. Yes, and the console can be called using a shortcut.
How many mouse clicks do you need to commit the code?

Answer 7

I do 80% of my work with git directly from Idea cmd+k cmd+t. It is already necessary to brunch and merge with the mouse. In confusing cases, gitk. When you want something strange, then the console.
But all the same, I would start from the console - it will give an understanding of how the git works.

Answer 8

Since some update, my console git has become colored - exactly since then I have stopped thinking about mastering some kind of gui for it.

Answer 9

I look at the commit history in PhpStorm and perform primitive actions, and everything else in the console.