Sass 3.3 is released • Hacker News Board

Re: Sass 3.3 is released

#21

Post by steveax » Sat, Mar 08, 2014, 7:42 PM UTC

bramdevries wrote: post #18

psychometry wrote: post #15

Earlier quoted context omitted.

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

If you're using dependency managers like bower you either have to import the stylesheet in your 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.

Just use the link to the CSS file in development an have your build tools concatenate everything for production. Certainly not a show stopper.

Re: Sass 3.3 is released

#22

Post by freshyill » Sat, Mar 08, 2014, 8:01 PM UTC

basicallydan wrote: post #14

hopfog wrote: post #3

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

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.

Re: Sass 3.3 is released

#23

Post by freshyill » Sat, Mar 08, 2014, 8:08 PM UTC

frankfang wrote: post #9

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

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!

Re: Sass 3.3 is released

#24

Post by gkya » Sat, Mar 08, 2014, 8:11 PM 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?

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.

Re: Sass 3.3 is released

#25

Post by LukeShu » Sat, Mar 08, 2014, 8:12 PM UTC

joemaller1 wrote: post #5

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

For some reason, at width

    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.

Re: Sass 3.3 is released

#26

Post by gruntmaster9000 » Sat, Mar 08, 2014, 8:17 PM 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?

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

Re: Sass 3.3 is released

#27

Post by gruntmaster9000 » Sat, Mar 08, 2014, 8:19 PM UTC

LukeShu wrote: post #25

joemaller1 wrote: post #5

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

For some reason, at width 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.

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

Re: Sass 3.3 is released

#28

Post by jacquesc » Sat, Mar 08, 2014, 9:18 PM UTC

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?

Re: Sass 3.3 is released

#29

Post by eropple » Sat, Mar 08, 2014, 9:29 PM UTC

gkya wrote: post #24

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?

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 probably wouldn't be using Sass at all.)

Re: Sass 3.3 is released

#30

Post by tyleregeto » Sat, Mar 08, 2014, 9:36 PM UTC

steveax wrote: post #20

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?

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

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.