Re:4 out of the 6 SO most voted questions are common Git issues
by bubuga on Thursday May 12, 2016 @11:04AM
(#11683886)
> The problem to me seem to be that Git is too powerful. It has many features built in and my guess is that the average dev uses a tiny fraction of them.
I don't understand why that is supposed to be considered a problem.
Everyone has their personal itch, and scratching that itch is more than enough to actually do your work.
No one needs to memorize a whole dictionary before getting to speak with someone.
> The XKCD comic is true, because for most people downloading a fresh copy is far easier than working out how to use git properly.
If a local repository is broken, would it be better to:
a) spend hours trying to debug it, pinpoint the problem, come up with a solution, pray it doesn't affect remote repos
or
b) download another copy?
Re:4 out of the 6 SO most voted questions are common Git issues
by collyw on Thursday May 12, 2016 @02:48PM
(#11685786)
Depends on the circumstances.
Need a fix in the next hour option a)
You are going to be working with a large team on a long term project, no deadlines are immediately pressing option b)
https://xkcd.com/1597/
The XKCD comic is true, because for most people downloading a fresh copy is far easier than working out how to use git properly.