They also support Mercurial, which I personally find to be a way better scm tool than git.

Not trying to start the classic hg vs git debate, just saying that it's great to have the option.

It's not better, it's just a million times more usable. A Ferrari is nice, but for day-to-day stuff I'd rather use a Volvo :)

The trick to git is figuring out the subset of commands that make it work like a Volvo

Why do that if you could just use hg?

Because everyone else is still using git.

There is a Mercurial extension that allows you to use hg commands to interact with a git repo

https://bitbucket.org/durin42/hg-git

My experience with hg-git has been that it is not always a great citizen with git repos and it can cause something of a mess. (This is a few years old now, because like the rest of the world I switched to git; it may have improved in the meantime.)

For some reason the enterprise version doesn't support mercurial, it's only git.

The reason is it's a completely unrelated product (previously known as "stash") that Atlassian pretends is somehow connected for branding reasons.

Yep, the two products are even written in separate languages!

Bitbucket Server is written in Java and bitbucket.org is written in Python.

I was dumbfounded when I found out they were two separate codebases.

I thought it's like JIRA. Or is JIRA self hosted also different from the cloud version?

I don't understand what you mean by "like JIRA". Remember all these Atlassian products have been acquired as what were originally separate companies.

...grumble grumble...Skype for Business...OneDrive for Business...

(hate it when companies do this)

It's because mercurial is legacy, like darcs, bzr, monotone, and the other zoo of "git-alikes" that were big in 2008. Now it's just like MacOS Classic in 2000: there are a few die-hard zealots who claim that the interface is better in some indescribable way, and everyone else has moved on.

Does this look like the commit log of a legacy product?

https://www.mercurial-scm.org/repo/hg/

Mercurial is very important for Facebook, Mozilla, Google, and others. The disparaging "legacy" monicker might be a good way to feel justified to not have to learn about it, but it's not dying software that is no longer getting updates.

Speaking as someone that works with Mercurial on daily basis, and also makes/sells software that supports Mercurial. I can tell you it's far from beeing legacy.

Some people work with COBOL on a daily basis. It's still antiquated.

What determines if a technology is considered legacy is not if there exists someone out there using it, but rather whether there are people actively adopting it at present. In this regard, Mercurial has slowed down and Git has clearly won the game.

There are companies adopting mercurial as they VCS of choice, either by moving out of svn, or choosing a new VCS

Bitbucket server is written in Java while Bitbucket.com in Python. Those are two different products. That's why the Enterprise version supports only GIT.

Check our RhodeCode for Enterprise SCM tool that supports Mercurial too.

Is RhodeCode still Pylons or have to migrated to Pyramid?

It's now based on pyramid 1.6