> 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

> 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?