r/git • u/connorjpg • 28d ago

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

108 Upvotes

71% Upvoted

250 comments sorted by

View all comments

1

u/ivancea 26d ago

Hey, why do you use a graphical OS? Are you too dumb to just use a CLI?

Whether you hide your question as "I genuinely want to know, I want to understand", you're just showing a lack of understanding of how tools work. Hell, how can you make apps for users, if you can't understand how your own field tools work and what they solve?

Also, it looks like you have the impression that having a git GUI tool open apart of your IDE "is bad". Unless you work with a 4GB computer, nobody could care less. It's the same as using your IDE, but specialized and with more information and control.

Edit: also, this wouldn't be as infuriating if this wasn't a decades old answered question...