3 ms·

While I don't dabble often in markup, I'm curious. Is Sass still mostly entrenched in the Ruby world (any alternative implementations?) or has it picked up ado

by joaomsa 13y ago

While I don't dabble often in markup, I'm curious. Is Sass still mostly entrenched in the Ruby world (any alternative implementations?) or has it picked up adoption with other devs compared to Less?

steveax 13y ago
There's lib-sass[1] a C implementation, but it's not at feature parity yet. [1] http://libsass.org http://libsass.org
- tyleregeto 13y ago
  Thanks for posting that! I started looking for an implementation that I could embed/distribute easier just the other day. I didn't stumble across this one and it looks promising. This is one area tools built on Ruby, Node, and similar platforms often fall short.
gkya 13y ago
There is nothing that requires Sass and other Ruby programs to be endemic to Ruby world. The programming language it is implemented in is an implementation detail after all.
- eropple 13y ago
  This is technically, and therefore the best kind of, correct, but in practical usage there's Ruby and JRuby and, uh...does it run in IronRuby? I mean, libsass is a thing, but it's not nearly feature-complete. You end up bolting a Ruby thing into your pipeline somewhere, which is a bit of a drag depending on how you're used to doing things. (For me, I just let Play handle it, but if somebody hadn't made play-sass I probably wouldn't be using Sass at all.)
  - gkya 13y ago
    I am not a designer, and the only place I use sass is a bunch of static blogs, including my primary one. The command I run to compile my sass files is as follows: find . -name '*.sass' | onchange -s make css where onchange is a simple command I've written that watches filesystem for events on files from stdin and runs command when they occur, and make css is simply sass --update _sass:dynamic/styles So long as sass is in the $PATH, I'm good to go. I don't care how my sass files are translated to css files, I only care whether they get translated or not. In the last place I worked, they used guard for compiling less (sth. like sass) files and concatenating them, which was a frightening program with a huge configuration file, written in JSON. For concatenation, I'd do find dynamic/styles -name '*.css' | onchange -s cat dynamic/styles/*.css > dynamic/all.css See, when your abstractions are processes, everything is easy. It's like git, one simply does not need to know if git commit is a shell script or a C program. It is a process, you need to call it, and that's it. edit: put in absent redirection into the last command line.
gruntmaster9000 13y ago
It’s seen wider acceptance. Some argue even more so than LESS. Sass is very popular in the Drupal community, for instance.
joemaller1 13y ago
Personally, Sass was the first tool to really push my toolset towards its current polyglot of whatever works best.

by joaomsa 13y ago

While I don't dabble often in markup, I'm curious. Is Sass still mostly entrenched in the Ruby world (any alternative implementations?) or has it picked up adoption with other devs compared to Less?

steveax 13y ago

There's lib-sass[1] a C implementation, but it's not at feature parity yet. [1] http://libsass.org http://libsass.org

tyleregeto 13y ago
Thanks for posting that! I started looking for an implementation that I could embed/distribute easier just the other day. I didn't stumble across this one and it looks promising. This is one area tools built on Ruby, Node, and similar platforms often fall short.

gkya 13y ago

There is nothing that requires Sass and other Ruby programs to be endemic to Ruby world. The programming language it is implemented in is an implementation detail after all.

eropple 13y ago
This is technically, and therefore the best kind of, correct, but in practical usage there's Ruby and JRuby and, uh...does it run in IronRuby? I mean, libsass is a thing, but it's not nearly feature-complete. You end up bolting a Ruby thing into your pipeline somewhere, which is a bit of a drag depending on how you're used to doing things. (For me, I just let Play handle it, but if somebody hadn't made play-sass I probably wouldn't be using Sass at all.)
- gkya 13y ago
  I am not a designer, and the only place I use sass is a bunch of static blogs, including my primary one. The command I run to compile my sass files is as follows: find . -name '*.sass' | onchange -s make css where onchange is a simple command I've written that watches filesystem for events on files from stdin and runs command when they occur, and make css is simply sass --update _sass:dynamic/styles So long as sass is in the $PATH, I'm good to go. I don't care how my sass files are translated to css files, I only care whether they get translated or not. In the last place I worked, they used guard for compiling less (sth. like sass) files and concatenating them, which was a frightening program with a huge configuration file, written in JSON. For concatenation, I'd do find dynamic/styles -name '*.css' | onchange -s cat dynamic/styles/*.css > dynamic/all.css See, when your abstractions are processes, everything is easy. It's like git, one simply does not need to know if git commit is a shell script or a C program. It is a process, you need to call it, and that's it. edit: put in absent redirection into the last command line.

gruntmaster9000 13y ago

It’s seen wider acceptance. Some argue even more so than LESS. Sass is very popular in the Drupal community, for instance.

joemaller1 13y ago

Personally, Sass was the first tool to really push my toolset towards its current polyglot of whatever works best.