Why SASS over LESS

I agree with the above comment.

I should mention I really do love the Zen Grids project being developed. Definitely going to save a lot of time for developers.

I was just wondering if there would be plans to port this code to LESS or include LESS as an alternative.

I myself prefer SCSS + Compass atm but with LESS having a huge contributor base (x5 that of SCSS) and twitter bootstrap being as awesome as it is, I wonder if it is beneficial to have both.

I could be wrong but porting from SCSS to LESS is fairly straightforward as both have same CSS3 syntax?

with LESS having a huge contributor base (x5 that of SCSS)

I'm curious where you found that statistic? URL please. :-)

Hey I should have elaborated I was comparing the Github statistics:

https://github.com/cloudhead/less.js has 5500 Watchers and 704 Forks

https://github.com/nex3/sass has 990 Watchers and 190 Forks

Arguably this does not take into account total popularity but can be seen as indicative of future growth. ^_^

If you compare https://github.com/nex3/sass/graphs/contributors to https://github.com/cloudhead/less.js/graphs/contributors, you'll see Sass has more contributors then Less.

Sadly, "watch"ing and "fork"ing doesn't correlate with contributing. They're about as useful a metric as "commits".

I need to write up a blog post about why I picked Sass over Less. But it was an active decision process that Matt Farina and I did near the beginning of last year. We evaluated both and picked Sass/Compass. We picked Sass mostly because it is a much more mature project, especially when you add Compass into the mix. The answer to "Does LESS have any supporting libraries that can compare to Compass?" seems quite lacking: http://stackoverflow.com/questions/5946187/compass-style-libraries-for-l...

I can't speak for John or anybody else, but here are our reasons for choosing SASS over LESS in our shop. We don't put too much emphasis on the number of contributors as long as the community is active and making significant progress, which is the case for SASS (there are more Honda Civic on the road, but we rather drive a Mercedes if we can afford it :-)

Our choice of SASS boils down to comprehensiveness of technical features, robustness of the "language" and as John mentioned, Compass, Compass and Compass. Can't say enough about Compass ... lol.

The comparison of SASS vs LESS is captured succinctly in this graph:

http://wrangl.com/sass-v-less

In our experience, SASS is a more mature "programming language" in that it provides conditional statements and operators (if then else) and looping (for{} loop), and feature like selector inheritance. Working within the Compass environment, SASS developers can either reuse existing frameworks like 960gs or create their custom CSS framework. It is so much easier to work in SASS within Compass.

And the Drupal community seems to catch on to SASS as witnessed by the number of recent themes that support SASS:

- Zen
- AdaptiveTheme
- Basic
- Boilerplate
- Sasson
- Aurora