> but I have a pretty hard time understanding why someone can't spend a week getting up to speed with a tool they intend to use for years to come. Because it m

> but I have a pretty hard time understanding why someone can't spend a week getting up to speed with a tool they intend to use for years to come. Because it may not be for enough years. I've used CVS, SVN, Git in less than 15 years. I still have clients on SVN because Git is too much to get to grips with. > what is it about Git that people find painful? Why is there no built-in 'tree' command? I am lost without my .gitconfig and the aliases I have set up to give me a visual view of the repository. Also, the difference between HEAD^3 and HEAD~3. I have muscle memory to do what I need, but for more occasional tasks I am searching StackOverflow. I haven't used other DVCS so I don't know if the pain points are Git, or they're the complexities that DVCS brings. I look forward to the next (r)evolution in source control, when I hope we have power but more human-friendliness.