4 ms·
Officially SCSS is the "primary syntax" and SASS merely the "old syntax that is still supported". I never understood the rationale behind this decision (does a
by moe 16y ago
Officially SCSS is the "primary syntax" and SASS merely the "old syntax that is still supported".
I never understood the rationale behind this decision (does anyone prefer SCSS over SASS?), but who cares as long as SASS remains a first-class citizen.
- rudiger 16y agoI prefer SCSS to SASS, but I like braces. I also find being a superset of regular CSS to be a plus (even though it's not something I've actually used in practice).
- tedunangst 16y agoSCSS lets me migrate an existing css file without rewriting anything and drop in random snippets I find on the web without translation. It solves exactly the problem I have (limited expressiveness) without introducing a new one (new syntax to learn).
- sync 16y agosass-convert is your friend and takes care of both of your problems for you.
- tedunangst 16y agoHow, and with what input and output formats? I said I like SCSS.
- jarin 16y agoIf you output to a file with a .scss extension it will auto-detect.
- Fluxx 16y agoI've only ever used SCSS, mostly cause it was the "official" version when I first used it. I also think that SASS files look weird to me...for whatever that's worth. SCSS eing a superset of CSS is huge too, IMO, as one of the bigger push-backs I get from lots of people on SASS is it's "another language to learn" and you don't get any benefit unless you convert everything. That goes away with SCSS.
- daemin 16y agoI prefer to use the SCSS syntax rather than the SASS syntax (and I've used both) mainly because I don't use HAML and I have a deep distrust of significant whitespace that is syntactically significant. The SCSS syntax works for me because it's like normal CSS but with extra useful features - functions, mixins, nesting, etc.