←back to thread

Oh Shit, Git?

(ohshitgit.com)
464 points Anon84 | 1 comments | 16 Jan 25 18:24 UTC | HN request time: 0.202s | source
Show context
SebastianKra ◴[16 Jan 25 20:29 UTC] No.42730483[source]▶
We should start recommending UIs as the default way to learn Git. It would solve a third of these problems and another third wouldn't even come up.

If you later decide that the CLI is faster, go ahead. But first, people need to see visually how they can interact with the tree.

I like fork.dev, but most clients are pretty similar at this point.

replies(14): >>42731131 #>>42731315 #>>42731362 #>>42731414 #>>42731485 #>>42731663 #>>42731730 #>>42732771 #>>42732796 #>>42732944 #>>42734694 #>>42739237 #>>42740117 #>>42747946 #
1. JTyQZSnP3cQGa8B ◴[16 Jan 25 21:54 UTC] No.42731414[source]▶
I agree, I have used git for more than 10 years and it's the only tool that I refuse to learn. The command-line interface is cryptic and infuriating. I'd rather write assembly language again than learn what is essentially a CLI to the internals of git. It's not high-level, it's not intuitive, and it can be destructive if you don't use the right option. I stick to GUIs and simple actions, and I never had any problems compared to all the horror stories of my CLI-loving coworkers.