In my case, I got accustomed to very rebase heavy workflows in git, and history rewriting in mercurial feels feels tacked on. With git, the repo is basically j

In my case, I got accustomed to very rebase heavy workflows in git, and history rewriting in mercurial feels feels tacked on. With git, the repo is basically just a DAG plus refs, and once you understand that model, it mostly makes sense. hg has... three? four? different ways to rewrite history, that all work in different ways under the hood. It's not that bad once you realize you should just use the evolve extension and ignore everything else, but as a novice it's hard to know which method to use, and it's not hard to stumble upon people recommending awful footguns like `rollback`.