Sass 3.3 is released(blog.sass-lang.com) |
Sass 3.3 is released(blog.sass-lang.com) |
Now you can finally use BEM in Sass without the need of verbose mixins. Good stuff!
So excited about this, absolutely brilliant. I did notice some frameworks that I was using (I think it was Bourbon) breaking with SASS 3.3 though.
I'm using it with rails, anyone able to get things working with sprockets, etc?
http://sass-lang.com/documentation/file.SASS_CHANGELOG.html#...
word-break: break-all
which sets the character-splitting to CJK (Chinese/Japanese/Korean), where splitting between characters is OK. This should generally not be used on English text.Perhaps the author meant to use
word-wrap: break-word
Which allows it to split a word that is too long to fit on a single line, instead of stretching/extending outside of the text area.Is Sass still mostly entrenched in the Ruby world (any alternative implementations?) or has it picked up adoption with other devs compared to Less?
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.)
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.