8 ms·

I would have liked to have seen LESS support dropped. Bootstrap is the only thing keeping LESS alive right now...

by hackerboos 12y ago

aikah 12y ago
I dont,I prefer LESS over SASS for multiple reasons(running less in the browser during development is one).
- jmathai 12y ago
  Is there a secret I don't know about or do browsers convert LESS to CSS natively?
  - mrkipling 12y ago
    No, but there's a JS file that transforms your LESS into CSS in the browser. It's handy for development but obviously you'd want to pre-compile for production.
    - jeffreyrogers 12y ago
      Is there any reason someone couldn't do the same thing for Sass?
      - bruce_one 12y ago
        looks plausible: http://medialize.github.io/sass.js/ http://medialize.github.io/sass.js/ :-)
      - drivingmenuts 12y ago
        The biggest issue is probably keeping up with Sass. Other Sass implementations are behind on features. Less ... well, there's less to keep up with since there's one implementation of it that I'm aware of. I used to prefer Sass, but mostly because it was the only thing going at the time, but I'm starting to lean toward Less.
  - deleted 12y ago
    [deleted]
- vlunkr 12y ago
  Use a pre-compiler then. Gulp is so fast you won't even notice the compilation time.
mattwad 12y ago
OTOH, without LESS a lot of us would have to add Ruby to our stack :p
- hackerboos 12y ago
  https://github.com/sass/node-sass https://github.com/sass/node-sass
  - eddiegroves 12y ago
    Does libsass work 100% with the Bootstrap sass port? Every time I've checked on libsass support it is behind the ruby version in some way.
    - e1g 12y ago
      Yes - we use libsass across the board, including building BS3, and have had no issues with compatibility. It used to have a problem with high precision numeric values (like "6.666666666%" in BS) but that's has been resolved.
  - illicium 12y ago
    > The libsass library is not currently at feature parity with the 3.2 Ruby Gem that most Sass users will use, and has little-to-no support for 3.3 syntax.
    - harlanlewis 12y ago
      Libsass is missing some hugely important features, but it (appears to be) in very active development and the disparity list is shrinking. Even lacking missing those features, the 12x compilation speed improvement in libsass is pretty compelling.
    - e1g 12y ago
      The note is slightly outdated - the recently released libsass V3[1] is targeting SASS 3.4, and they expect to fully pass the spec by V3.1
rayshan 12y ago
Less still appears to be significantly more popular than Sass (sources: github / npm stats, not perfect sources but likely directionally correct)
- cheapsteak 12y ago
  How much of that is due to Bootstrap though?
jrochkind1 12y ago
There is a Sass port of bootstrap that is labelled 'official' and is in the same github project as the 'canonical' less version: https://github.com/twbs/bootstrap-sass https://github.com/twbs/bootstrap-sass It's already got a 3.3.0 available, it is kept sync'd. I have very occasionally run into a bug or problem with the sass port not being kept properly parallel to the original less, but mostly it just works fine.
- sfilipov 12y ago
  Just tried creating a Compass project with bootstrap-sass 3.3.0, ran into this problem: https://github.com/twbs/bootstrap-sass/pull/757 https://github.com/twbs/bootstrap-sass/pull/757 Releasing the LESS and Sass versions at the same time is a bit premature. Looks like the Sass version wasn't tested as much.
  - jrochkind1 12y ago
    Yeah, I have run into that too previously, with "QA" on the Sass port not being as good as one might ideally like. But, hey, look, they already released 3.3.0.1 of the sass version fixing the problem, 3 hours after the ticket was filed, that's pretty responsive, sometimes that's the most you can ask for. (Part of the issue is it's not JUST a Sass version, people expect a Sass version that works with Compass with or without Rails, and that works with Rails without Compass, and that works with Sprockets without Rails, and that works standalone with nothing but Sass just compiling css like the Less version, and each context has it's own picadillos).

I would have liked to have seen LESS support dropped. Bootstrap is the only thing keeping LESS alive right now...

aikah 12y ago

I dont,I prefer LESS over SASS for multiple reasons(running less in the browser during development is one).

jmathai 12y ago
Is there a secret I don't know about or do browsers convert LESS to CSS natively?
- mrkipling 12y ago
  No, but there's a JS file that transforms your LESS into CSS in the browser. It's handy for development but obviously you'd want to pre-compile for production.
  - jeffreyrogers 12y ago
    Is there any reason someone couldn't do the same thing for Sass?
    - bruce_one 12y ago
      looks plausible: http://medialize.github.io/sass.js/ http://medialize.github.io/sass.js/ :-)
    - drivingmenuts 12y ago
      The biggest issue is probably keeping up with Sass. Other Sass implementations are behind on features. Less ... well, there's less to keep up with since there's one implementation of it that I'm aware of. I used to prefer Sass, but mostly because it was the only thing going at the time, but I'm starting to lean toward Less.
- deleted 12y ago
  [deleted]
vlunkr 12y ago
Use a pre-compiler then. Gulp is so fast you won't even notice the compilation time.

mattwad 12y ago

OTOH, without LESS a lot of us would have to add Ruby to our stack :p

hackerboos 12y ago
https://github.com/sass/node-sass https://github.com/sass/node-sass
- eddiegroves 12y ago
  Does libsass work 100% with the Bootstrap sass port? Every time I've checked on libsass support it is behind the ruby version in some way.
  - e1g 12y ago
    Yes - we use libsass across the board, including building BS3, and have had no issues with compatibility. It used to have a problem with high precision numeric values (like "6.666666666%" in BS) but that's has been resolved.
- illicium 12y ago
  > The libsass library is not currently at feature parity with the 3.2 Ruby Gem that most Sass users will use, and has little-to-no support for 3.3 syntax.
  - harlanlewis 12y ago
    Libsass is missing some hugely important features, but it (appears to be) in very active development and the disparity list is shrinking. Even lacking missing those features, the 12x compilation speed improvement in libsass is pretty compelling.
  - e1g 12y ago
    The note is slightly outdated - the recently released libsass V3[1] is targeting SASS 3.4, and they expect to fully pass the spec by V3.1

rayshan 12y ago

Less still appears to be significantly more popular than Sass (sources: github / npm stats, not perfect sources but likely directionally correct)

cheapsteak 12y ago
How much of that is due to Bootstrap though?

jrochkind1 12y ago

There is a Sass port of bootstrap that is labelled 'official' and is in the same github project as the 'canonical' less version: https://github.com/twbs/bootstrap-sass https://github.com/twbs/bootstrap-sass It's already got a 3.3.0 available, it is kept sync'd. I have very occasionally run into a bug or problem with the sass port not being kept properly parallel to the original less, but mostly it just works fine.

sfilipov 12y ago
Just tried creating a Compass project with bootstrap-sass 3.3.0, ran into this problem: https://github.com/twbs/bootstrap-sass/pull/757 https://github.com/twbs/bootstrap-sass/pull/757 Releasing the LESS and Sass versions at the same time is a bit premature. Looks like the Sass version wasn't tested as much.
- jrochkind1 12y ago
  Yeah, I have run into that too previously, with "QA" on the Sass port not being as good as one might ideally like. But, hey, look, they already released 3.3.0.1 of the sass version fixing the problem, 3 hours after the ticket was filed, that's pretty responsive, sometimes that's the most you can ask for. (Part of the issue is it's not JUST a Sass version, people expect a Sass version that works with Compass with or without Rails, and that works with Rails without Compass, and that works with Sprockets without Rails, and that works standalone with nothing but Sass just compiling css like the Less version, and each context has it's own picadillos).