You might not need JavaScript classes
summary
Argues that using classes in JavaScript often creates surprises: prototype is a live object so changing it affects existing instances, classes lack true privacy and static features, and methods bound per instance become per-instance bound methods (extra functions, worse minification and tree-shaking). Proposes concrete alternatives: closure-based factories and object composition, plus real examples where frameworks migrate to functions like React hooks and Vue composition, showing equal capability with simpler, safer runtime behavior.
AI-written summary · about
chapters (8)
- 0:00Introduction and context
- 2:26Roadmap of the presentation
- 3:11Why classes were introduced
- 5:59Common pitfalls of classes
- 15:58Functional alternatives
- 25:50Frameworks moving away
- 35:12Summary and conclusions
- 38:26Q&A session
