Ask HN: Thoughts on Sass

We've been using Sass in production since we launched. Love it.<p>I've not seen any real comparison between LessCSS and SCSS (i.e. the new Sass syntax that became available with Sass version 3.0) There were some real differences before that, but that's not nearly so clear to me anymore.<p>At present, we've decided that there's no reason to use LessCSS as we already use Haml and there's nothing that Less offers that gives us a reason to switch from recent versions of Sass. I'm not even sure what the differences are now.

I think it genuinely addresses some of the design flaws of css (too much repetition). That can't be bad. But I'm not sure a new syntax needs to be created for the job. I'm having a little play with using plain json to represent css in a similar style: <a href="http://github.com/twfarland/son" rel="nofollow">http://github.com/twfarland/son</a> (on node.js/express). There are still some things I need to add (firebug integration, creating actual css files) but it seems helpful so far.

I'm using it in production in multiple places, and I <i>adore</i> it. I will never go back.<p>If you want to just dip your toes in, look at SCSS. It's a superset of CSS, so you can take your existing stylesheets and start using more advanced features.<p>That said, I prefer pure SASS. It's cleaner, IMO, forces better organization, and is less typing.

I recommend checking out <a href="http://lesscss.org/" rel="nofollow">http://lesscss.org/</a> - haven't used SASS recently, not sure how well it compares these days. Used to be not as powerful as Less.