On the Spectrum of Abstraction
summary
Argument claims abstraction level decides tradeoffs and shows when to prefer functions over data, using examples like 5,000 stars on react motion, the concrete property gained by Redux time-travel via immutability, and why Gulp over Grunt wins when build requirements move. Concrete evidence includes which tools trade expressivity for analyzability (templates, Glimmer), how micro modules multiply cost, and concrete rules: shave use cases for performance, prefer small API surface, and ship copy‑paste examples.
AI-written summary · about
chapters (18)
- 0:00Introduction
- 5:03Definitions
- 7:51Pareto Principle
- 8:31Libraries vs Framework
- 10:17Writing code is easy
- 10:51Getting your abstraction wrong
- 14:34We seek more power
- 16:24Case studies
- 17:02Grunt vs declarative DSL
- 19:02What do you want
- 20:08React vs templates
- 23:29Views and models
- 25:21Mutability vs immutability
- 26:27JavaScript vs Traditional CSS
- 30:45Copypaste
- 32:04JS Fatigue
- 33:04Use Examples
- 33:58Conclusion
related talks
07mA New Kind of Abstraction
07mA New Kind of Abstraction
19mFinding Your Abstraction Sweet Spot
26mThe Power Of Small Abstractions
45mAbstraction Considered Harmful (and other opinions about writing maintainable code)
25mThe Intro to Abstraction I Wish I'd Received
29m"Turtles all the way down: Abstractions and when we should use them"
17mThe Myth of Perfect Abstractions