> "Tired of all the slow and bloated preprocessors..."
libsass is amazingly fast. I generally see it churn through ~20k lines of CSS (don't ask) in 6ms.
libsass is amazingly fast. I generally see it churn through ~20k lines of CSS (don't ask) in 6ms.
That said, Sass encourages practices that I consider bad. Nesting, @extend, etc.
Sass's design also makes it difficult to implement a basic feature like grouping all media queries for a single output. Check this issue from 2011: https://github.com/sass/sass/issues/116
If you don't mind a bigger tool and the dependency on Node.js, then PostCSS looks very good: https://github.com/postcss/postcss
Representing hierarchy in the class name makes the output shorter, in most cases, and makes the HTML and CSS code easier to understand. For instance, when you see <div class=title>, you need to go up to find context to understand what that "title" class is. If you have <div class=widget-title>, that's much better. Let alone that generic ("title") classes can lead to problems with conflicting rules depending on their specificity.
By the way, classes at the top level are faster to parse and apply.
This articles expands on some of these issues: http://www.sitepoint.com/beware-selector-nesting-sass