The ability to evaluate statements at runtime. Sass needs to be compiled ahead of time and you therefore can’t alter your sass based on the state of your JavaScript.
You can react to state-changes directly in your css, instead of having to toggle classes and you can have theming that you don’t know about at compile-time (this is getting there with css-variables too, but that’s not something sass has to offer). But other than that there isn’t any killer features - you get sass + a little extra for a insignificant performance penalty.
For me personally I really like the Vue-approach of having your css written in the same file as your component. It completely eliminates the fear of removing css, scoping issues and specificity problems. Its not for everyone though.
Thanks for the elaboration. For something animation heavy I see the benefits where there are lots of animated and updated CSS rules. For standard admin style UI stuff, not so much.
1
u/kowdermesiter Mar 07 '19
What's the killer feature that SASS doesn't have?