Why SASS stopped being the primary syntax (now SCSS is the one)?

Question

In the official webpage they say:

Although no longer the primary syntax, the indented syntax will continue to be supported.

Doe anybody know why SCSS "partially took over" SASS?

Answer 1

The concepts that Sass addresses aren't obvious to designers, and this means that Sass has always been misunderstood as nothing more than a different, quirky syntax for writing CSS.

(LESS.css has gained a little buzz among designers, probably because its syntax is more similar to CSS — even though Sass is more capable and robust, regardless of syntax.)

Because Sass is a language for authoring styleshets, it needs to be approachable to designers. The whitespace-aware Sass syntax is perceived as a "completely different" language with little functional gain, and the different syntax isn't everyone's cup of tea. The valuable concepts like variables, mixins, subclasses (@extends), unit arithmetic, color math, etc. go right over people's heads if they can't get past the "weird" syntax.

SCSS was designed to be a true superset of CSS. This means anyone can start with a plain CSS file and their knowledge of CSS, and then introduce concepts gradually without being overwhelmed.

The sass-convert utility makes the choice of syntax a moot point: if you prefer Sass over SCSS like I do, it's easy to switch.