<i>Corporate America needs a centralized version control system. Subversion still offers this: Subversion centralizes the repository and simply checks out a working copy (versus Git, which gives you a complete repository). Corporate America still needs to have cannonical version numbers, and the ability to see the progress of a product over time as a single line – not a bunch of branches and independent repositories.</i><p>While I think I understand what he is saying, there isn't any reason why Git can't be used just like SVN (other than checking out only the latest version, which I wouldn't argue is an advantage).  Just because you can branch and merge easily in Git doesn't mean that you have to.<p>Edited to add the following:<p>There are some valid reasons for not using Git over SVN, but I find it pretty hard to believe that better branching/merging, offline repo access, and version numbers are among them.<p>Moving on from something which is already in place and taking care of existing needs, or better GUI tools (in "Corporate Americal" anyway) are certainly valid.