"CSS in JS - The good, The bad and The ugly"
summary
Starts from the claim that CSS-in-JS solves global namespace and dead CSS problems but at the cost of runtime work and fragmentation: about 40+ libraries with different APIs, some like CSS Modules or styled-components and Emotion either compile to CSS or generate classes at runtime. Scoped styles and no dead code are real wins, but surprising costs include many generated classes, extra rerenders, runtime stylesheet injection, SSR and caching complexity, and portability headaches across projects and frameworks.
AI-written summary · about
chapters (4)
related talks
26mCSS in JS: The Good & The Bad Parts
28mSee the Past, Present, and Future of CSS-in-JS
23mCSS-in-JS
24mA thorough analysis of CSS-in-JS
31mUnique Value Proposition of CSSinJS and the Future
58mCSS in JS: What For and Why?
31mCSS in JS: Is it worth the hype
25mCSS is dead, long live CSS but in modules, please!