3 ms·

Maybe we should start calling this something besides inline styles, because of the huge negative connotation it carries. It's more like component-ized styles or

by vlunkr 11y ago

Maybe we should start calling this something besides inline styles, because of the huge negative connotation it carries. It's more like component-ized styles or something. This is a pretty interesting concept though. I've noticed that in really large and interactive web apps sass becomes super unwieldy, and many styles just aren't re-usable.

davidkpiano 11y ago
Look at the source. It's quite literally inline styles.
- olefoo 11y ago
  I think what vlunkr is trying to say is that perhaps we shouldn't be as contemptuous of inline style information as the design community has been over the past 10 years.
- baby 11y ago
  isn't it more like multilines style?
- vlunkr 11y ago
  Sure that's the final result, but like mmatants said, it's the opposite of how inline styles were used back in the day. They were static then, and repetitive, the idea here is to programmatically create inline styles for web pages that have become increasingly dynamic and complex.
mmatants 11y ago
Generated styles? And great point - these new inline/generated styles are the opposite of what they meant 10 years ago (copy-pasta hacks). Now they are even more powerful than regular CSS, instead.
- Lazare 11y ago
  Easier, maybe. But they're actually less powerful; inline styles support a strict subset of what regular CSS supports. (eg, no support for pseudo elements, as others have mentioned)
  - acjohnson55 11y ago
    Not to mention you lose the ability to live edit classes of elements all at once in the dev tools -- pretty hand for tweaking layouts of prototypes.
  - acjohnson55 11y ago
    Not to mention you lose the ability to live edit classes of elements all at once in the dev tools -- pretty hand for tweaking layouts of prototypes.
  - acjohnson55 11y ago
    Not to mention you lose the ability to live edit classes of elements all at once in the dev tools -- pretty hand for tweaking layouts of prototypes.

by vlunkr 11y ago

davidkpiano 11y ago

Look at the source. It's quite literally inline styles.

olefoo 11y ago
I think what vlunkr is trying to say is that perhaps we shouldn't be as contemptuous of inline style information as the design community has been over the past 10 years.
baby 11y ago
isn't it more like multilines style?
vlunkr 11y ago
Sure that's the final result, but like mmatants said, it's the opposite of how inline styles were used back in the day. They were static then, and repetitive, the idea here is to programmatically create inline styles for web pages that have become increasingly dynamic and complex.

mmatants 11y ago

Generated styles? And great point - these new inline/generated styles are the opposite of what they meant 10 years ago (copy-pasta hacks). Now they are even more powerful than regular CSS, instead.

Lazare 11y ago
Easier, maybe. But they're actually less powerful; inline styles support a strict subset of what regular CSS supports. (eg, no support for pseudo elements, as others have mentioned)
- acjohnson55 11y ago
  Not to mention you lose the ability to live edit classes of elements all at once in the dev tools -- pretty hand for tweaking layouts of prototypes.
- acjohnson55 11y ago
  Not to mention you lose the ability to live edit classes of elements all at once in the dev tools -- pretty hand for tweaking layouts of prototypes.
- acjohnson55 11y ago
  Not to mention you lose the ability to live edit classes of elements all at once in the dev tools -- pretty hand for tweaking layouts of prototypes.