When comparing Fossil SCM vs Hexo, the Slant community recommends Hexo for most people. In the question“What are the best solutions for a personal blog?” Hexo is ranked 7th while Fossil SCM is ranked 25th.
Ranked in these QuestionsQuestion Ranking
Pro All in one
While most other platforms allow either online blogging, or development offline and hosting on some other platform, fossil allows you to develop locally, host it locally, view it locally, and you can substitue locally with remote if you want to.
It's just one file. Fossil.
It is. It is also free as in libre, as in the license is similar (or equivilant) to BSD-2
Pro Simple to use
Fossil doesn't depend on a specific language to be present on the target or development system. Just write, commit, and done.
Pro Fast and easy to use
Pro Deployment is easy and fast
Hexo built sites can be easily deployed to Github pages, Heroku, Openshift (custom cartridge needs to be setup) or any other custom solution (just copy over the
public folder). Any deployment is as simple as editing the
_config.yml file and running the
Pro Generating a blog is pretty fast
Generating a new blog with Hexo is generally really fast. Hexo truly lives up to it's name as a simple and fast static website generator.
Pro Constantly updated and actively maintained
Hexo's repository in GitHub is very active and it's actively being maintained. Updates are released every two or three months.
Pro Complete and helpful documentation
Hexo's documentation is very thorough and helpful, especially for people who are just starting with it.
Con You have to do everything manually and know what you're doing
It is similar to the "Writing your own solution" option
Con Relatively large community but the majority is non-english speakers
Hexo has a relatively large following and community, especially in China. While this is certainly a positive, many developers who do not know chinese would be unable to follow all the guides and tutorials out there written by their chineses counterparts.