You might not need JavaScript classes
summary
Argues that ES2015 classes create false expectations because they’re syntactic sugar over live prototypes (changing a prototype mutates existing instances), lack true private/static fields in current JS, and force fragile context binding (this) which often turns methods into per-instance functions. Demonstrates with a counter and a movie-API example, shows factory/closure patterns, modules and object composition as alternatives, and cites React Hooks and Vue Composition API as real-world moves away from classes. closures and composition offered as practical replacements.
AI-written summary · about
chapters (7)
- 0:00Introduction
- 3:55Why JavaScript got classes
- 6:26Problems with classes
- 16:27Alternatives with functions
- 26:03Frameworks dropping classes
- 37:47Recap and key takeaways
- 39:54Q&A
