Hacker News new | past | comments | ask | show | jobs | submit login

My biggest issue with a GUI is that most that I've seen introduce new terms for various stuff, e.g. "sync" in VS Code, or "revert commit" (in Source Tree maybe?) — there's no Git command called "sync" or "revert", so I'm not immediately sure what they do.

In a CLI I know exactly what's happening.

That's just my opinion though. If people feel comfortable working in a GUI all the more power to them.




Git does have a revert command.


Yeah, my bad. Must've been "reverse" then. I just remember the revert/reverse dichotomy.


Or perhaps it called revert but it wasn’t doing a git revert, it was doing a git checkout to simulate an SVN revert... I’ve seen this in at least one GUI. That kind of crap just makes it harder to unwind problems when things go wrong and to learn the tool.


> no Git command called ... "revert"

Maybe not in the way Source Tree uses it, but there certainly is[1]! I've had to use it a few times.

> git-revert - Revert some existing commits

[1] https://git-scm.com/docs/git-revert


My bad, then it was "reverse" in Source Tree (or whatever it was).


I like Magit because it doesn't try to hide git while still giving all the advantages GP mentioned https://magit.vc/


I work with a lot of people who have no idea how git actually works and it is infuriating. They all use the git desktop program, and almost every time I get called over to help, it’s because they didn’t sync or refresh or whatever the hell it does.

If you don’t have a good mental model for git, you’re gonna have a bad time.


Second this. I was one of those people that needed help when I was learning git. Went full CLI after that and never looked back.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: