I used CVS and ClearCase before moving into Git, and it took me some time to adjust to the fact that the cost of branching in Git is much much less than ClearCase. And getting into the “distributed” mindset didn’t happen overnight.
I used CVS and ClearCase before moving into Git, and it took me some time to adjust to the fact that the cost of branching in Git is much much less than ClearCase. And getting into the “distributed” mindset didn’t happen overnight.
The completely useless error messages kill me. And the commands that don’t do what they say… WTF is the point in “clean” and “force” if they don’t clean or force? And then there’s the inconsistency in command arguments. With one you have to use force, even though it doesn’t actually force, and the other you have to use “hard”. Hard? I mean I guess hard makes sense once you realize that force doesn’t actually mean force. Now I’m just waiting to run across the switch “–seriouslyguysimeanitthistime”.
OMG, I can’t up vote this thread enough… git is such a purposefully exclusionary step in software development that I can’t believe it is the preferred solution. It is very powerful, but it is painfully obvious that no one has ever gone back and said, “but what if anyone else who wants to use this is not a Linux cli guru and already has an expert understanding of git commands?”. Why is it that learning to check in code is significantly harder than learning the actual IDEs that the devel uses to develop the code?
This x100. I mean I think I know the answer - Git was written by a C kernel guy, and the devs that it attracted are C guys. The kind of people who think user friendliness is a weakness. Guess how you contribute a patch to Git? Well step 1 is reading a 10 page essay… Needless to say that isn’t going to attract many people that care about beginners.