Re:Some bad Git situations and how I got myself out of them
by ubernostrum on Friday September 09, 2016 @03:18PM
(#12465280)
Are you suggesting a Git user will eventually need to understand it? That's a strike against Git already.
The typical advice -- which you'll see in this thread and elsewhere -- is that anyone who uses git should learn git's internals, and preferably up-front, since apparently that will magically cause git to make sense.
I'm a bit put off by the idea, myself.
Re:Some bad Git situations and how I got myself out of them
by exDM69 on Friday September 09, 2016 @03:48PM
(#12465512)
Exactly.
It's also worth looking at git internals because it's very elegant, clean and simple. In my opinion, one of the best designed software systems I've come across.
I encourage you to look at the README in the first git commit, it's very enlightening.
Re:Some bad Git situations and how I got myself out of them
by whataretensors on Friday September 09, 2016 @09:19PM
(#12467174)
>Are you suggesting a Git user will eventually need to understand it? That's a strike against Git already.
I think as engineers we should understand how our tools work.
I'm only an occasional Git user, but am a heavy Mercurial user.
I have never needed to understand Mercurial's internals.
Are you suggesting a Git user will eventually need to understand it? That's a strike against Git already.
From my observation over the years, people who use Git get "stuck" more often, because they are trying to leverage the extra power Git seems to provide. With Mercurial, you often can do similar powerful stuff, but they make sure you have to go through hoops to do it. As such, unsuspecting non-power users do not shoot themselves in the foot.