A Series of Unfortunate Effects
summary
Claims that modelling effects as data yields composable, manipulable computations but pays costs: using monad transformers fixes composition by nesting structures yet forces extra layers everywhere and kills performance; free monads and a freer encoding represent effects as data and enable interpretation, and combining them with open unions and heterogeneous lists produces a working extensible effects system, but it relies on heavy type‑level machinery and complex transformations so it works technically yet is impractically complex for broad adoption.
AI-written summary · about
chapters (15)
- 0:00Intro
- 0:27Lore
- 1:36Side Effects
- 2:28The Kingdom of Haskell
- 4:06The Problem with Effects
- 5:08Nested Effects
- 6:01The Programmer
- 8:20Nesting
- 11:10Retaliating
- 12:24New Idea
- 16:00Side Effect
- 18:05Free Monads
- 23:28Transformations
- 24:32Extensible Effects
- 26:18Epilogue
related talks
01h 06mThe Evolution of Effects
43mFunctional Programming with Effects
50mFunctional Programming with Effects
43mSurviving a world overflowing with effects
31mThe Eff monad, one monad to rule them all
33mExtensible Effects: A Leaner Cake for Purely Functional Code
21mCompositions for Free: Reasoning about Effectful Lenses
14mFundamentalist Functional Programming