3 ms·
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. https:/
by collyw 11y ago
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.
https://xkcd.com/1597/ 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.
- na85 11y ago>because for most people downloading a fresh copy is far easier than working out how to use git properly. A true and stinging indictment of git's poor ui/ux
- bubuga 11y ago> 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?
- collyw 11y agoDepends 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)