I think of it as returning CSS to what it's good at: styling small trees. By making components responsible for their own internal
state, reduce the "bleed through" that makes managing styles so painful.
Good progress being made on part/theme: https://www.chromestatus.com/feature/5763933658939392 …
-
-
The result, however, was always going to be that people wrote components in a single file. That file included all of these parts; the arguments about delivery format are now separate thanks to the rise of (too much?) tooling.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Care to elaborate on what you mean by "declarative community"...? because I'd argue that JSX + CSS-in-JS is equally declarative. It's just using declarative DSLs instead of static templates.
-
If you're really selective about how you use the word by strategically ignoring the parts that aren't declarative. But, yes, they are semi-declarative. And have good sides. The way JSX rationalizes to DOM methods is something I always find interesting.
- 16 more replies
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
& Web Standards TL; Blink API OWNER
Named PWAs w/
DMs open. Tweets my own; press@google.com for official comms.





)
