Sass 3.3 is released • Hacker News Board

Re: Sass 3.3 is released

#31

Post by gkya » Sat, Mar 08, 2014, 10:11 PM UTC

eropple wrote: post #29

gkya wrote: post #24

Earlier quoted context omitted.

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.

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 pr…

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.

Re: Sass 3.3 is released

#32

Post by joemaller1 » Sun, Mar 09, 2014, 12:34 AM UTC

joaomsa wrote: post #19

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?

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

Re: Sass 3.3 is released

#33

Post by hobonumber1 » Sun, Mar 09, 2014, 3:57 AM UTC

I'm not a Sass expert here, but does anyone know if anything in this release helps with the problem of not being able to @extend items within media queries?

Re: Sass 3.3 is released

#34

Post by scottkellum » Sun, Mar 09, 2014, 1:23 PM UTC

freshyill wrote: post #22

basicallydan wrote: post #14

Earlier quoted context omitted.

AlwaysTwisted has a really great guide on this for more info and copy-and-pastability. http://alwaystwisted.com/post.php?s=2014-02-27-even-easier-b... 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 think they've been waiting on Sass 3.3 to release the next Bourbon update. There have been pull requests that were accepted long ago (hyphens mixin comes to mind) that still aren't in the released version of Bourbon.

Agreed this would be great but I would be curious to see how Bourbon would deal with their extensive and growing LibSass user base which has the feature set of Sass 3.1.

Re: Sass 3.3 is released

#35

Post by scottkellum » Sun, Mar 09, 2014, 1:26 PM UTC

hobonumber1 wrote: post #33

I'm not a Sass expert here, but does anyone know if anything in this release helps with the problem of not being able to @extend items within media queries?

Yes, the new [@at-root](https://github.com/nex3/sass/blob/master/doc-src/SASS_CHANGE...) directive. It is verbose but will allow you to extend root level extends. However this creates selector spaghetti in your CSS and should be avoided if possible.