It's just some kind of script. It is not CSS.
No one claimed it was CSS.
Sass 3.3 is released
11–20 of 35 posts
Re: Sass 3.3 is released
#12Still 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.
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#...
That adds a CSS import rule, doesn't embed the content.
Re: Sass 3.3 is released
#13Whatever line-wrap/justification setting they're using is horribly, illegibly broken on mobile Safari. Some irony.
It doesn't look good on mobile Chrome, either, and in horizontal mode the menu overlay dominates almost half the screen.
Looking very good here at latest chrome on latest Android.
Re: Sass 3.3 is released
#14> 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.
Re: Sass 3.3 is released
#15Still 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.
What's so bad about having to rename a file?
Re: Sass 3.3 is released
#16Earlier quoted context omitted.
It doesn't look good on mobile Chrome, either, and in horizontal mode the menu overlay dominates almost half the screen.
Looking very good here at latest chrome on latest Android. http://imgur.com/kuSeXfn
I wouldn't call random, non-hyphenated word breaks like that "looking very good"!
Re: Sass 3.3 is released
#17Sass 3.2.15 was also released today. I'm staying with it for a while to avoid breaking anything I have right now.
Re: Sass 3.3 is released
#18Still 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.
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.
Re: Sass 3.3 is released
#19While 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?
Re: Sass 3.3 is released
#20While 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.