Re:Inline CSS works better in a component world
by IfOnlyYouKnew on Thursday August 20, 2020 @05:18AM
(#24221426)
Cascading / depending on the parent's style are features specifically intended to enable a component-based approach. It allows, for example, to use h1's in your component, but have them render at appropriate sizes depending on their level in the overall hierarchy.
[ Parent
| on HN ]
Re:Inline CSS works better in a component world
by lioeters on Thursday August 20, 2020 @02:24PM
(#24226631)
Cascading is, to me, like class inheritance in object-oriented style of programming. Useful in some cases, but can become unmanageable with more than a few layers.
The "inline CSS" approach is an escape hatch to avoid cascading styles. I can see its advantages, to apply all (and only) the styles on the component level.
Re:Inline CSS works better in a component world
by lioeters on Thursday August 20, 2020 @05:40PM
(#24229342)
Apparently someone didn't appreciate the jab at OOP. Well, I call it like I see it - seen more messes made by class inheritance and cascading, than without.
Re:Inline CSS works better in a component world
by type0 on Thursday August 20, 2020 @06:38PM
(#24229843)
There's also this grouping method to separate classes https://piccalil.li/cube-css/
it's cringe at first but so was BEM and it's still useful even if you combine both