The Rise of Modular Style
summary
Claims that CSS gains a module system now translate into concrete pieces: a tiny intermediate format called Interoperable CSS that adds :import and :export pseudo‑directives, a CSS Modules compiler that rewrites classes into safe hashes and emits a JS mapping, and toolchain glue for webpack/browserify with no runtime dependency. Composing replaces Sass extend to avoid selector bloat, shared atoms let many components reuse the same rules, and a dependency graph enables future dead‑code removal; the work is recent but already interoperates with existing bundlers.
AI-written summary · about
chapters (15)
- 0:00Glen Maddern The Rise of Modular Style
- 3:03JavaScript in 2008
- 6:10Interoperable JavaScript Modules March 21, 2009 Kris Kowal
- 7:11"Whatever Node Does" became the standard
- 8:12Sweet JavaScript History Lesson Dude!
- 9:45Browserify September 5, 2011
- 10:28You can change the human interface of a language without needing to change the machine interface.
- 11:19None of these change the global nature of CSS
- 18:37Part 2 Modular Style
- 20:11The number of mistakes a new developer makes when learning to use a system is a value judgement of the system. not the developer
- 25:36Break the 1-to-1 mapping between entities and classes
- 27:38Single Purpose Files full of Single Purpose Classes
- 28:32Define an API into your styles for your markup to use
- 28:44Modular Style?
- 29:24Flexibility
