Sass 3.3 is released (opens in new tab)

(blog.sass-lang.com)

75 pointsFWeinb12y ago31 comments

31 comments

> You can now write &-suffix (or &_suffix, or even &suffix if you really want) and Sass will make it work.

Now you can finally use BEM in Sass without the need of verbose mixins. Good stuff!

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.

freshyill12y ago

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.

1 more reply

jacquesc12y ago

It's been a real bummer using sass the last 6-12mo with no sourcemaps support in chrome. It used to work, then Chrome changed something and it all went to hell.

I'm using it with rails, anyone able to get things working with sprockets, etc?

nbody12y ago

Still can't import pure CSS files without having to rename them to .scss. It's been in talks for over two years now, very disappointing.

hopfog12y ago

I don't remember if I've tried it but I thought this was fixed in 3.0.

http://sass-lang.com/documentation/file.SASS_CHANGELOG.html#...

nbody12y ago

That adds a CSS import rule, doesn't embed the content.

psychometry12y ago

What's so bad about having to rename a file?

bramdevries12y ago

If you're using dependency managers like bower you either have to import the stylesheet in your <head> or use the @include in a sass stylesheet, both will be a new HTTP request. Whereas if you compile it in one file, you save an extra request (now imagine you use multiple dependencies each with their own css file). Renaming a file would defeat the whole point of dependency management.

1 more reply

joemaller112y ago

Whatever line-wrap/justification setting they're using is horribly, illegibly broken on mobile Safari. Some irony.

LukeShu12y ago

For some reason, at width <= 480, it sets

    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.

gruntmaster900012y ago

The blog theme was made by a Chinese developer, which is probably why that is set the way it is.

carbocation12y ago

It doesn't look good on mobile Chrome, either, and in horizontal mode the menu overlay dominates almost half the screen.

xfalcox12y ago

Looking very good here at latest chrome on latest Android.

http://imgur.com/kuSeXfn

1 more reply

joaomsa12y 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?

steveax12y ago

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

[1] http://libsass.org

tyleregeto12y 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.

gruntmaster900012y ago

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

gkya12y 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.

eropple12y 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.)

1 more reply

joemaller112y ago

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

hobonumber112y ago

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?

scottkellum12y ago

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.

Brajeshwar12y ago

Sass 3.2.15 was also released today. I'm staying with it for a while to avoid breaking anything I have right now.

frankfang12y ago

It's just some kind of script. It is not CSS.

freshyill12y ago

Thank you for weighing in, professor. Yeah, I really can't imagine why would anybody ever care about this tool that tens or hundreds of thousands of people use every day to build web interfaces. Especially here, on Hacker News, of all places. What is the world coming to? It's not even CSS!

ceejayoz12y ago

No one claimed it was CSS.

j / k navigate · click thread line to collapse

31 comments

hopfog12y ago

> You can now write &-suffix (or &_suffix, or even &suffix if you really want) and Sass will make it work.

Now you can finally use BEM in Sass without the need of verbose mixins. Good stuff!

basicallydan12y ago

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.

freshyill12y ago

1 more reply

jacquesc12y ago

It's been a real bummer using sass the last 6-12mo with no sourcemaps support in chrome. It used to work, then Chrome changed something and it all went to hell.

I'm using it with rails, anyone able to get things working with sprockets, etc?

nbody12y ago

Still can't import pure CSS files without having to rename them to .scss. It's been in talks for over two years now, very disappointing.

hopfog12y ago

I don't remember if I've tried it but I thought this was fixed in 3.0.

http://sass-lang.com/documentation/file.SASS_CHANGELOG.html#...

nbody12y ago

That adds a CSS import rule, doesn't embed the content.

psychometry12y ago

What's so bad about having to rename a file?

bramdevries12y ago

1 more reply

joemaller112y ago

Whatever line-wrap/justification setting they're using is horribly, illegibly broken on mobile Safari. Some irony.

LukeShu12y ago

For some reason, at width <= 480, it sets

    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.

gruntmaster900012y ago

The blog theme was made by a Chinese developer, which is probably why that is set the way it is.

carbocation12y ago

It doesn't look good on mobile Chrome, either, and in horizontal mode the menu overlay dominates almost half the screen.

xfalcox12y ago

Looking very good here at latest chrome on latest Android.

http://imgur.com/kuSeXfn

1 more reply

joaomsa12y 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?

steveax12y ago

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

[1] http://libsass.org

tyleregeto12y ago

gruntmaster900012y ago

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

gkya12y 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.

eropple12y 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?

1 more reply

joemaller112y ago

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

hobonumber112y ago

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?

scottkellum12y ago

Brajeshwar12y ago

Sass 3.2.15 was also released today. I'm staying with it for a while to avoid breaking anything I have right now.

frankfang12y ago

It's just some kind of script. It is not CSS.

freshyill12y ago

ceejayoz12y ago

No one claimed it was CSS.

j / k navigate · click thread line to collapse