Was it obvious because he specifically notes it in the intro to the article?
Note: I’m a long-time advocate of Git, and a contributor to the project, so I am biased (but I hope my conclusions are not).
He failed to do so, but we couldn't know that without reading the article.
[1]: http://felipec.wordpress.com/2011/01/16/mercurial-vs-git-its...
That was not the case.
What I said is that they are basically the same, except for the handling of branches, not history rewriting as you suggest.
I assume you agree that they are basically the same, now, if you disagree that the handling of branches is superior in git, feel free to add a comment in my blog, but after 160 comments, nobody has managed to contradict that conclusion.
So no, nobody has managed to prove where exactly is the bias. It is possible that git is superior, and that's what the evidence suggests.
That's not even true, history is allowed to be rewritten in mercurial (mercurial-bundled extensions `rebase`, and `mq` as well as the standard `rollback` command do — or can be used to do — exactly that, and so do third-party extensions such as `histedit`), there's little difference on that point. The difference is the tendency to push for history-rewriting.
> but that's splitting hairs.
Not being completely and utterly wrong is "splitting hairs"?
Furthermore, it makes very little sense to criticize a tool with no basis in the tool's capabilities themselves but based merely on its community's suggestions, do you also criticize Python because its community recommends underscore_separated method names and you prefer camelCase? I'm not saying the community is not important, but mercurial itself, as a tool, has absolutely no hangup on history rewriting.
He is right on one thing: the differences are mostly subtle, the most glaring one being whether history is allowed to be rewritten or not. In the end it all comes down to personal preferences, and my personal experience is strongly in favor of hg.