Many other build tools have to make repeated reads and writes to process a single file. Mimosa reads and writes once.
Mimosa's core config and feature set are shared by all of its modules. Mimosa's defaults and conventions keep your config DRY.
Mimosa may have web development as its primary goal, but Mimosa is a multi-purpose task runner. Mimosa even builds itself.
Mimosa's modules know what to execute and when to execute it. They don't need to be told what to do. You'll spend less time configuring Mimosa applications.
Use Mimosa's command line to build out a skeleton app that is ready to go with transpilers, pre-processors, and a server if you need one. Or use a pre-built skeleton or example app already equipped with your favoriate libraries.
Sane defaults keep you coding instead of figuring out config. If you stick to the conventions you may never look at or update the configuration. But Mimosa is heavily configurable if you ever need to vary away from its conventions.
Live reload, Bower, NPM, jshint, eslint, ember.js, and the list goes on. And if the one you deeply need doesn't exist, bridging the gap is a piece of cake.
SASS, Less, Stylus, CoffeeScript, 6to5, Handlebars, Jade and dozens of others. Writing a compiler module is easy, so there plenty from which to chose.
Karma, Testem, QUnit, and Mocha are a few of the testing modules out there, some with deep intergrations with libraries like Ember.
Mimosa's AMD/require.js support is second to none, but if commonjs & browserify are your thing, there are modules for that too.
Give Mimosa a few minutes and it will transform your development workflow.Get Started