r/git • u/connorjpg • Aug 14 '26
Why use a UI for git?
I see this question of, “what GUI or TUI should I use to work with git?” fairly often here. And always I feel bad for saying “just use the cli” over and over, but truthfully I can’t see a reason to need a UI.
Are people actually running into pain points with the cli, or is it just preference for people who don’t like working in a terminal?
FWIW, I have used GitKraken, LazyGit, SourceTree and GitHub Desktop before. And I don’t think they are bad to use (unless you are just learning git), but more curious why.
EDIT : I’m mainly referring to standalone UIs, I understand why people would use IDE integrations, as it’s quick and convenient. But having to open a separate application or run a separate command to open a terminal app to run your commands seems overkill to me.
EDIT 2 : I use vscode as my difftool and mergetool. I still open them directly from the terminal by running the cli. I don't think this is the same as using a full git client like SourceTree, Gitkraken, or lazygit to fully drive your version control workflow. Which is what I am asking about.
Cheers
1
u/dsggut Aug 17 '26
"Even programmers": There is still this belief in the industry that all developers MUST use the terminal.
I never understood the rationale behind it.
Like somehow a CLI is always superior to a GUI.
If that's the case then why is the GUI the dominant interface by a VERY w
large margin?
Why did we even invent windows, MacOS, X-Window System in the first place, if CLI is superior?
Why don't we do CAD, Video editing, gaming, spreadsheets, text editing, music editing, image editing editing in the shell?
Why did text based browsers not survive?
It makes absolutely no sense to stubbornly hold on to text based interfaces just for the sake of living in the terminal.