4 ms·

I've avoided the CSS preprocessors for some reason, something about learning a CSS pseudo-language just didn't feel right. The idea behind this however is aweso

by xauronx 13y ago

I've avoided the CSS preprocessors for some reason, something about learning a CSS pseudo-language just didn't feel right. The idea behind this however is awesome. You're writing simple, true CSS and it does the annoying work of making it crappy CSS that browsers want. I might actually be able to get behind this.

marknutter 13y ago
There's nothing to learn. Even if you use nothing more than nesting it's a huge boon to productivity and readability.
- xauronx 13y ago
  Well, I don't know how to do nesting right now so there WOULD be something to learn :D Maybe it was that a clear winner never arose between LESS and SASS or maybe that I always let things play out a bit before jumping onto a trendy technology. I guess I'll have to just get with it since it's not really going away.
  - sergiotapia 13y ago
    It's literally: .header { background-color: orange; p { font-size: 16px; } } You nest the selectors and it spits out .header{} and .header p {}. Much cleaner to write and maintain.
    - xauronx 13y ago
      Well, now I learned something. Also, that's pretty awesome. I could definitely use that.
- dreamfactory 13y ago
  It's replacing a declarative syntax with a procedural one as far as I understand which is a huge (and unwelcome) shift.
stormcrowsx 13y ago
You've been missing out avoiding CSS preprocessors, they're fun.
dabernathy89 13y ago
I avoided preprocessors for a while too, but I can't imagine not using SASS now. Even if all it had to offer was nesting it would be worth it, but with variables and mixins it really shines.
zem 13y ago
there's nothing about "true css" that makes it intrinsically superior to the "pseudo-languages" that have to be preprocessed to generate css. the spec merely determines the features browsers have to support, not the manner in which people have to use them.
marquis 13y ago
This very good intro to SASS makes it really obvious. https://www.youtube.com/watch?v=fPAf8dN4G4w https://www.youtube.com/watch?v=fPAf8dN4G4w
valtron 13y ago
You can also write colors with the more intuitive hsl() and it'll convert them to hex notation. (Only relevant if you need to support IE < 9, but still cool.)

by xauronx 13y ago

marknutter 13y ago

There's nothing to learn. Even if you use nothing more than nesting it's a huge boon to productivity and readability.

xauronx 13y ago
Well, I don't know how to do nesting right now so there WOULD be something to learn :D Maybe it was that a clear winner never arose between LESS and SASS or maybe that I always let things play out a bit before jumping onto a trendy technology. I guess I'll have to just get with it since it's not really going away.
- sergiotapia 13y ago
  It's literally: .header { background-color: orange; p { font-size: 16px; } } You nest the selectors and it spits out .header{} and .header p {}. Much cleaner to write and maintain.
  - xauronx 13y ago
    Well, now I learned something. Also, that's pretty awesome. I could definitely use that.
dreamfactory 13y ago
It's replacing a declarative syntax with a procedural one as far as I understand which is a huge (and unwelcome) shift.

stormcrowsx 13y ago

You've been missing out avoiding CSS preprocessors, they're fun.

dabernathy89 13y ago

I avoided preprocessors for a while too, but I can't imagine not using SASS now. Even if all it had to offer was nesting it would be worth it, but with variables and mixins it really shines.

zem 13y ago

there's nothing about "true css" that makes it intrinsically superior to the "pseudo-languages" that have to be preprocessed to generate css. the spec merely determines the features browsers have to support, not the manner in which people have to use them.

marquis 13y ago

This very good intro to SASS makes it really obvious. https://www.youtube.com/watch?v=fPAf8dN4G4w https://www.youtube.com/watch?v=fPAf8dN4G4w

valtron 13y ago

You can also write colors with the more intuitive hsl() and it'll convert them to hex notation. (Only relevant if you need to support IE < 9, but still cool.)