FP vs OO: Choose Two
summary
Argues the FP vs OO split is a false dichotomy and gives concrete guidance: use functional core techniques inside modules and boundary shell OO for I/O, failure, versioning and security. Points to real artifacts — ConcurrentHashMap and the ForkJoinPool on the JVM — as examples of code that must be encapsulated and that work in practice, and cites Scala and Clojure leveraging the JVM ecosystem. Claims the largest FP codebases stay smaller than the largest OO systems and recommends mixing paradigms deliberately.
AI-written summary · about
chapters (15)
- 0:00Intro
- 1:37Sports
- 4:20Cultural Anthropology
- 6:06Functional vs OO
- 7:17Learning from multiple paradigms
- 11:15What is OO
- 14:26What is a program
- 15:41Object vs Function
- 16:36Everything is an Object
- 17:40The Problem to Solve
- 19:12Building Abstractions
- 20:38Platform Libraries
- 23:46Boundaries
- 29:22Complexity
- 31:57Conclusion
