This article is within the scope of WikiProject Internet, a collaborative effort to improve the coverage of the Internet on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.
it is not Syntactic sugar by definition, as it is not the same language before (sass) and after (css).
I find the term “interpreter” at least not perfect: This does not happen at runtime of the final code. (Apart from being more of a description language anyhow). I believe “preprocessor” is a better term.
Sass has traditionally been developed in Ruby, then ported to C, however the maintainers behind announced in a blog post that they would be switching to Dart, and no longer maintaining the Ruby branch. The Ruby version will be maintained for 1 year, then abandoned unless an open source volunteer decides to maintain it. source: http://blog.sass-lang.com/posts/1022316-announcing-dart-sass — Preceding unsigned comment added by 126.96.36.199 (talk) 13:55, 30 November 2016 (UTC)
The "mixins" section seems contradictory. In one sentence is says Sass doesn't support mixins, and then goes on to describe Sass mixins and show their syntax. Someone who understands what it really supports needs to clarify this paragraph. -- Finlay McWalterჷTalk 14:55, 14 September 2013 (UTC)
I'm a web developer and cannot understand this article. "Sass is a scripting language that is interpreted into Cascading Style Sheets (CSS)". By whom? Who interprets it? The browser? The server? What's its support? Do you need to install an Apache module on the server side that will "compile" Sass into "normal" CSS, which will be read and interpreted by the browser? Do you need an extension in your browser? Please, can anyone clarify this?