<i>>My recommendation to other people facing similar decisions is to choose the project that has a brighter future, chances are the “disadvantages” you see in the present would be resolved soon enough.</i><p>That's not what I would recommend at all. There's no guarantee a project will resolve those issues or that new ones will crop up. Google was correct in choosing hg because it was the best choice <i>at the time</i> (back in 2008).<p>It looks like his only positive point are the branches, and then goes on to say, "The conclusion shouldn’t be that surprising; Git wins." I'd imagine hg being supported in Windows without requiring a third party install is a big plus.<p>I think the first comment puts it nicely: <a href="http://gitvsmercurial.com/" rel="nofollow">http://gitvsmercurial.com/</a><p>----------- edit -----------<p>It looks like the author had a discussion in the comments:<p><i>>My objective is to show why Git is superior. So if you care about your own performance, and the one of your project, the choice is obvious. One allows you to do many things, the other one doesn’t.</i><p>However, this contradicts his previous statement that the differences between the two are subtle and only proves his bias is heavily influencing his conclusion.