To be fair, running “apt install steam” and it promoting to remove the base packages is a pretty bad bug, and the safeguard they’ve put in place since that incident in case you remove your entire distro was long overdue. If he were using it in a professional setting? Skill issue, read the output. But he was using it… as a user!

Sure, if you want to do it once, but Git still has to compute that information (save for a new-ish cache that is just that, a cache). But that is not the point really, the point is that Mercurial’s graph Is the same (topologically) everywhere, which is not the case in Git because branches (and thus remotes) have different names. So saying that a branch contains a commit is not the same as a commit being on a branch. There are a bunch of great properties that emerge from this but it’s too long for this comment and I should actually properly write this down at some point this year.

Given that Git and Mercurial were both created around April 2005 to serve the same purpose by very similar people for the same reason… I’d say it’s fair!

It’s still here and very much alive in case you were curious.

As one of the maintainers of Mercurial, I take great offense in this meme. ;)

Strong disagree. Commit messages that are only one sentence long should be reserved for truly trivial things. Signed, someone who regularly comes back to 18+ year old commits and enjoys the valuable details that would have been lost.

In my experience and that of most of my friends both French and German, that is wrong. The French rail system may have its flaws (it does), but the German one is so much worse

While I agree that people should have moved on for a while, the idea that porting Python 2 to 3 only involves “find and replace” or a tool like 2to3 is only true in the most trivial cases. Anything that touches bytes, unicode, network or files to do anything remotely involved needs a lot more care. I should know, our codebase still suffers from the occasional bug due to this, even though it’s been years.