When comparing Mercurial vs Fossil, the Slant community recommends Mercurial for most people. In the question“What are the best version control systems?” Mercurial is ranked 2nd while Fossil is ranked 3rd. The most important reason people chose Mercurial is:
Mercurial is a more intuitive option than many of its competitors. The [documentation](https://mercurial.selenic.com/guide) is well organized and easy for beginners to read & understand.
Ranked in these QuestionsQuestion Ranking
Pro Easy to use
Mercurial is a more intuitive option than many of its competitors. The documentation is well organized and easy for beginners to read & understand.
Pro Free and open source
Mercurial is open source and free to use.
Doesn't require access to a central repository, because each checkout is a full repository by itself.
Pro Same features Git provides, but much easier to use and to understand
The command-line interface is more intuitive, requiring much less memorization and exotic options/piping to achieve the same thing you would in git.
Mercurial is designed to make performing operations (such as commits, clones etc.) fast.
Pro Native Windows support
Native Windows support. No trace of cygwin or other dirty hacks typically found in competitors.
Pro Good documentation
Mercurial documentation covers everything from revision control system basics to mercurial specific features in a short and clear way.
Users can activate plugins to provide additional features.
Pro Fully python based
Pro Doesn't delete history
Mercurial makes it pretty darn hard to delete history by mistake. In Git, if you mistakenly commit to HEAD and switch to a different branch, your commit is toast. Yes, you can dig through the reflog but most users don't even know of its existence and will wish they didn't once they find out.
Pro Actively contributed to by Facebook
Mercurial is actively contributed to by the developers at Facebook as they use it for their massive source repository.
Pro Very complete
Fossil includes source code management, bug tracking, a wiki, and technotes.
It even includes its own web server, though it can fairly easily be incorporated into other webservers.
A Fossil repository is contained in a single file.
Fossil can run on Linux, Mac, BSD derivatives and on Windows.
Pro Very easy to configure as self-hosted.
Single, stand-alone executable, including web server.
Pro Needs very few server resources
Since Fossil is a distributed VCS on top of being a bug tracker, it needs very few server resources.
Con Lost the widely adopted race to git
Sharing code and projects in an open source world is a must and trying to working with multiple Source Code Control systems does not help the ecosystem.
Con Can't delete named branches
You pretty much have to use tags instead.
Con Feels limited from a Git user's perspective
E.g. it does not offer the ability to rebase/force-push your own feature branch.
Con Setup paths are hardcoded
Con Only a web interface or CLI
Fossil's bug tracker only works with the web interface or the command-line interface. There's no native GUI client supporting it.
There are some independent GUI clients out there, but none of them support Fossil's full range of abilities.