3 ms·
To me, it's obvious that the author has entered the comparison with a very strong git bias, so it is only naturally that git won eventually. He is right on one
by BerislavLopac 15y ago
To me, it's obvious that the author has entered the comparison with a very strong git bias, so it is only naturally that git won eventually.
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.
- parfe 15y ago>To me, it's obvious that the author has entered the comparison with a very strong git bias, so it is only naturally that git won eventually. 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).
- eipipuz 15y agoThat's not obvious. He clearly says he hopes his conclusions would go beyond his bias. He failed to do so, but we couldn't know that without reading the article.
- BerislavLopac 15y agoLOL no, I missed that one. But the sibling is correct, the author failed.
- felipec 15y agoSaying "the author failed" is easy. Presenting a case that demonstrates so is not. 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.
- eslaught 15y agoThe author seems to contradict himself in a comment[1]: My objective is to show why Git is superior. (Thanks to [2] for noticing.) [1]: http://felipec.wordpress.com/2011/01/16/mercurial-vs-git-its-all-in-the-branches/#comment-5773 http://felipec.wordpress.com/2011/01/16/mercurial-vs-git-its... [2]: http://news.ycombinator.com/item?id=3437677 http://news.ycombinator.com/item?id=3437677
- felipec 15y agoIt's not a contradiction. Note the word why. If in the analysis it turns out I fail to show that git is indeed superior, I would have to agree mercurial is superior, or they are equal. That was not the case.
- masklinn 15y ago> the most glaring one being whether history is allowed to be rewritten or not. 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.
- BerislavLopac 15y agoOK, "supposed" might be a better choice than "allowed"; but that's splitting hairs.
- masklinn 15y agoNo, "supposed" is almost as incorrect, mq is there in the standard distribution and most of its job is history rewriting (the mere act of popping a patch effectively rewrites history). `rebase`'s sole job is rewriting history. > 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.
- BerislavLopac 15y agoI'm sorry? Which tool was I criticizing exactly?
- stevecooperorg 15y agoYeah, this wasn't a straight comparison, but an act of apologetics.