Functional programming vs. Object-oriented Programming
summary
Compares concrete features: shows a Haskell map implementation and recursive Fibonacci to demonstrate lazy evaluation and pattern matching, then inspects Ruby’s practical tradeoffs—mutable strings, freezing, symbols, procs/lambdas and destructive methods—showing how immutability, higher‑order functions and pattern matching have been grafted onto OOP. Cites Stack Overflow language popularity to note no mainstream purely functional languages, points out memoization and faster tests (no DB) as tangible wins, and concludes hybrid use of FP patterns in OOP code reduces bugs and improves performance.
AI-written summary · about
chapters (12)
- 0:00Introduction and speakers
- 1:26Battle between paradigms
- 2:47Functional vs OOP spectrum
- 5:00Declarative vs imperative
- 6:28Fibonacci in Haskell
- 12:43Map function deep dive
- 20:12Functional patterns in Ruby
- 27:44Handling side effects
- 31:20Pattern matching in Ruby
- 32:22Adopting functional patterns
- 34:30Conclusion and survey
- 37:39Q&A session
related talks
53mOOP vs FP
34mPrinciples of functional programming with examples in Java and Haskell
59mForget OO and Think Functionally!
31mFrom OOP to FP
44mFunctional Programming You Already Know
33mBetter Ruby through Functional Programming
51mOOP v̶s̶ and FP
56mFunctional Programming on .NET - The Best of Both Worlds