4 ms·

The main reason I chose LESS was because of bootstrap support, I'm extremely happy with it and can't believe I didn't start with it before. I'll see how this p

by Trufa 13y ago

The main reason I chose LESS was because of bootstrap support, I'm extremely happy with it and can't believe I didn't start with it before. I'll see how this port goes, but I've read some good stuff about SASS: http://css-tricks.com/sass-vs-less/ http://css-tricks.com/sass-vs-less/ Any other points anyone can make for SASS against LESS?

riffraff 13y ago
I think since that article came out sass included a new very nice feature in the form of mixins[0]. Also, Compass[1] is awesome when working with sass, but I don't know if there is a less equivalent. [0]http://sass-lang.com/guide#6 http://sass-lang.com/guide#6 [1]http://compass-style.org/ http://compass-style.org/
- lowboy 13y ago
  I used to be a proponent of Compass, but I started using Bourbon[0] and Neat[1] and enjoy them more. They don't require a project definition, nor do they provide a utility to compile Sass, they're just a mixin library. And that suits me. [0] http://bourbon.io http://bourbon.io [1] http://neat.bourbon.io http://neat.bourbon.io
timdorr 13y ago
SASS is backed by Ruby, so you can take advantage of all of Ruby's power, including reading from the filesystem. For instance, combined with Compass, you can read image sizes and automatically pull in width and height for a class. Or you can more easily make sprite images via a mixin that knows the size of the image and how many rows/columns you have. I've been using bootstrap-sass since it was targeting bootstrap 2.3. They've done a great job of keeping up with bootstrap development, so it's great to see them officially supported. It wouldn't shock me at all if Bootstrap eventually moved over to SASS officially in the future.
- WalterSear 13y ago
  Actually, I moved away from Sass >because< of the Ruby tie in. Transpiling Sass to css using Ruby was using up most of my day. It's a dog! Fortunately, now there is node-sass and it's grunt wrapper, making for vastly faster transpiling process. https://github.com/andrew/node-sass https://github.com/andrew/node-sass
  - steveklabnik 13y ago
    There's been work to re-write sass in C (or C++), preliminary reports showed it being 4,000x faster, IIRC.
    - zachlatta 13y ago
      https://github.com/hcatlin/libsass https://github.com/hcatlin/libsass
      - lowboy 13y ago
        +1 for libsass. I started using Gulp instead of Grunt for a project, and gulp-sass uses libsass. My compilation times are now sometimes sub-millisecond (albeit with only 500 lines of scss spread across 4-5 files).
    - radq 13y ago
      This benchmark suggests it's more on the order of 10x? http://www.solitr.com/blog/2014/01/css-preprocessor-benchmark/ http://www.solitr.com/blog/2014/01/css-preprocessor-benchmar...
      - steveklabnik 13y ago
        Neat! It was only partially ported when I last heard numbers, full support often slows things down quite a bit.
    - glebm 13y ago
      As of a few days ago it is complete enough to compile bootstrap-sass :) https://github.com/hcatlin/libsass/issues/231#issuecomment-33248428 https://github.com/hcatlin/libsass/issues/231#issuecomment-3...

by Trufa 13y ago

riffraff 13y ago

I think since that article came out sass included a new very nice feature in the form of mixins[0]. Also, Compass[1] is awesome when working with sass, but I don't know if there is a less equivalent. [0]http://sass-lang.com/guide#6 http://sass-lang.com/guide#6 [1]http://compass-style.org/ http://compass-style.org/

lowboy 13y ago
I used to be a proponent of Compass, but I started using Bourbon[0] and Neat[1] and enjoy them more. They don't require a project definition, nor do they provide a utility to compile Sass, they're just a mixin library. And that suits me. [0] http://bourbon.io http://bourbon.io [1] http://neat.bourbon.io http://neat.bourbon.io

timdorr 13y ago

SASS is backed by Ruby, so you can take advantage of all of Ruby's power, including reading from the filesystem. For instance, combined with Compass, you can read image sizes and automatically pull in width and height for a class. Or you can more easily make sprite images via a mixin that knows the size of the image and how many rows/columns you have. I've been using bootstrap-sass since it was targeting bootstrap 2.3. They've done a great job of keeping up with bootstrap development, so it's great to see them officially supported. It wouldn't shock me at all if Bootstrap eventually moved over to SASS officially in the future.

WalterSear 13y ago
Actually, I moved away from Sass >because< of the Ruby tie in. Transpiling Sass to css using Ruby was using up most of my day. It's a dog! Fortunately, now there is node-sass and it's grunt wrapper, making for vastly faster transpiling process. https://github.com/andrew/node-sass https://github.com/andrew/node-sass
- steveklabnik 13y ago
  There's been work to re-write sass in C (or C++), preliminary reports showed it being 4,000x faster, IIRC.
  - zachlatta 13y ago
    https://github.com/hcatlin/libsass https://github.com/hcatlin/libsass
    - lowboy 13y ago
      +1 for libsass. I started using Gulp instead of Grunt for a project, and gulp-sass uses libsass. My compilation times are now sometimes sub-millisecond (albeit with only 500 lines of scss spread across 4-5 files).
  - radq 13y ago
    This benchmark suggests it's more on the order of 10x? http://www.solitr.com/blog/2014/01/css-preprocessor-benchmark/ http://www.solitr.com/blog/2014/01/css-preprocessor-benchmar...
    - steveklabnik 13y ago
      Neat! It was only partially ported when I last heard numbers, full support often slows things down quite a bit.
  - glebm 13y ago
    As of a few days ago it is complete enough to compile bootstrap-sass :) https://github.com/hcatlin/libsass/issues/231#issuecomment-33248428 https://github.com/hcatlin/libsass/issues/231#issuecomment-3...