On the other hand, I'd say that absent sufficient data, one should pick the most flexible tool, which I'll bet in this context is the one with the most moving parts, i.e. git.
Outside of the Git fanboy bubble, developers don’t want to have to be version control experts, which once you get past a certain level of Git usage, you have to be, whether you wanted to or not.
Especially if your team doesn’t have that person who can get you out of any Git jam you may get yourself into.
It will also be much faster to get a new developer up to speed using Sapling than Git. And because it’s Git-compatible, if there’s something super advanced that can only be done using the Git command line, that’s still an option.
Telling the intern/junior developer to read the man page for git-log is a non-starter; it’s over 19,000 words!
The best thing for the greybeards is they can continue using Git while others use Sapling and commit to the same repo.
To be fair, if I had a junior dev who couldn't skim a man page of 19 000 words, I would have freestanding concerns about their ability to contribute -- being able to inhale knowledge is a core competency of any engineer.
That said, I hear you when you say that most folks (think) they have better uses of their attention.
I daresay they're wrong, but it's not my place to dictate terms to anyone's curiosity, my own included!
Outside of the Git fanboy bubble, developers don’t want to have to be version control experts, which once you get past a certain level of Git usage, you have to be, whether you wanted to or not.
Especially if your team doesn’t have that person who can get you out of any Git jam you may get yourself into.
It will also be much faster to get a new developer up to speed using Sapling than Git. And because it’s Git-compatible, if there’s something super advanced that can only be done using the Git command line, that’s still an option.
Telling the intern/junior developer to read the man page for git-log is a non-starter; it’s over 19,000 words!
The best thing for the greybeards is they can continue using Git while others use Sapling and commit to the same repo.