Functional programming for fun and profit!!
summary
Functional techniques translate into concrete Ruby practices: prefer immutable value objects (use dry-struct or the new data class (Ruby 3.2 preview)) so state never surprises, make behavior into pure functions by dependency injection and returning transformed copies instead of mutating, and leverage actor-style concurrency ideas from Elixir/OTP where millions of Elixir processes run lightweightly; Ruby offers Ractors for parallelism but they remain experimental and require immutable data or copying to move objects between reactors.
AI-written summary · about
chapters (7)
- 0:00Start
- 2:51Programming paradigms
- 6:34Immutability: Why??
- 11:01A pure function
- 18:44Elixir's concurrency model: Actors
- 20:14Ruby's concurrency abstraction: Ractor
- 24:03Resources: Functional programming architecture
related talks
44mFunctional Programming for Rubyists
33mBetter Ruby through Functional Programming
42mTaking inspiration from the functional world
44mReal-World Functional Ruby
40mMake Ruby Functional Again!
37mFunctional Programming in Ruby
27mFunctional Ruby and the (big) dependency diet
40mFunctional Programming For The Anxious Developer
