I understand #git just fine and like it the best of any VCS I've used. Am I weird?
If people are having trouble learning it, it sounds like the problem is the training materials. What training materials did you use that were inadequate?
POV of a tech writer:
IMHO, git is so hard to learn because the devs chose to name everything as obscurely as possible.
Why call it "blame" when it does not blame anyone but rather adds revision info. "Stash the changes in a dirty working directory away"? Why is it dirty now? "git commit --all", except it does not commit all changes. And WTF is "porcelain format" again?!
Like, whenever you open the docs, it feels like using the "pick-axe interface" on your "HEAD" until it "bisects".
@Crell git beats any other VCS with ease.
Of course it have a few weird things, it's going on for ages now.
For most uses you need to understand a couple of concepts and commands and you're set.
You can setup practically anything and any process with it, and find answers for the problems with one search on the web.
Don't know why people are raging about it recently. 🤷
@Crell agreed. I’m far from a #git expert but it does all I need it to do, and definitely beats everything else I’ve ever used by mile, nay an astronomical unit
@awoodsnet I did the same. I didn't grok all the plumbing bits, but the main parts I got. I also had a Git-fu colleague at the time who walked me through stuff, which helped.
@Crell it's been fine for me, but the occasional advanced operation ends up being an arcane dark incantation, undertaken with only extreme trepidation.
But then, I used to use cvs, and my only other baselines of comparison are Subversion and Perforce, so 🤷
Add comment