Middleman vs Roots

Minification and compression are as easy as setting a few configuration options, and unique asset hashes are available to allow you to invalidate the cache of files that change regularly.

Middleman supports lots of compiled languages, such as Less, Markdown, Textile, CoffeeScript, Stylus and more.

Middleman has a resources page full of official and community extensions.

Replace your Gulp, Grunt, Bower configs

Middleman follows established conventions so if you know rails, you can easily pick up middleman.

Roots has heavy corporate sponsorship and is worked on very actively as a full time job. That means you can rely on it.

You can deploy to heroku, github pages, s3, etc. with a single command.

Roots supports dynamic content like jekyll for every compiler and language.

Roots is currently in the process examining how to leverage newer technologies to make Roots even better. You can see the new project on github: https://github.com/carrot/roots-mini

Here is the blog post explaining the next phase of Roots: https://medium.com/@jescalan/eaa10c75eb22#.uacjziaej

Here is the stack they're experimenting with:

- jade - for markup
- babel - for JS and JS transforms
- postcss - for CSS transforms
- webpack - as the core compiler

As this is a work in process, it just means the future of Roots continues to look great.

Not only does roots support a huge number of languages and compilers out of the box, it also allows you to insert custom compilers if you want. Fun fact, roots is the only static site generator that supports dogescript

Roots compiles files once for each extension, which allows for some advanced options if you get to that stage

Roots will precompile your templates into js, which makes it really smooth to work with client-side MV* frameworks.

Since roots is written in node, everything is compiled in parallel rather than in series, making it very quick.