The Dangers of Object-Oriented Designs
summary
Argues that using JavaScript classes promotes hidden mutable state and implicit cross-object references, leading to monolithic systems and heavy dependency-injection use. Presents evidence from constructors, methods that read many implicit fields, and brittle tests, and proposes alternatives: plain data structures with pure functions, algebraic pattern matching, and message-passing models (Erlang actors or Seneca-style services) to make dependencies explicit and easier to test.
AI-written summary · about
chapters (5)
- 0:00OOP design dangers
- 6:50Implicit object dependencies
- 13:30Constructors and serialization
- 19:01Functional vs OOP trade-offs
- 24:10Q&A
