Looks appealing, but it is very confusing. At least with Sass/less etc you can easily distinguish between native css and non-native css constructs such as mixins and extends. But the additions rucksack make are ambiguous. Is it real spec, future spec or something that rucksack developers have added for convenience?<p>I'd prefer nextCSS with all the spec being based on what is actually going to make in into CSS. Otherwise it's the same downsides as preprocessing languages with the added bonus of not being able to easily tell what lines are native to css or not.
This is neat, but you're removing any ability to customize each of the sub-modules you're using. Something like how PreCSS does it would be helpful: <a href="https://github.com/jonathantneal/precss/blob/master/index.js#L49-L64" rel="nofollow">https://github.com/jonathantneal/precss/blob/master/index.js...</a>