FP: The Good, the Bad and the Ugly
summary
Claims that functional programming boosts productivity by relying on immutability and purity, with purity letting signatures describe behavior and enabling “puzzle coding.” Concrete performance tests show an imperative array populate is about 10× faster than a naïve FP version on the JVM, and Scala’s List.map uses loops under the hood for speed. Practical fixes include tooling and compiler work: Metals, bloop and incremental compilation reduce friction and make FP viable in real projects.
AI-written summary · about
chapters (32)
- 0:00Intro
- 1:15The Good the Bad the Ugly
- 3:00Life is not like this
- 4:05Immutability
- 6:15Purity
- 7:15Signature
- 8:02Puzzle coding
- 9:25Learning curve
- 10:09Categorical programming
- 10:37Category theory
- 11:40Whats red midnight
- 12:14Burritos
- 12:38Lasagna
- 13:54Tutorials
- 15:24Rockstar Developer Syndrome
- 16:28No Maintainability
- 16:51Leaders
- 17:43Ugly Bits
- 18:04Break the Rules
- 19:59Benchmarking
- 22:11JVM Patterns
- 22:57Map Implementation
- 25:27Performance
- 26:39C is not perfect
- 27:35Scala Compiler
- 31:10Book
- 32:00ObjectOriented Programming
- 35:08How do you unboard newcomers
- 36:33How do you convince managers to use Scala
- 38:38How do you work with other people
- 40:25Purity of FP
- 43:15Questions
related talks
51mPragmatism, Puritanism and Functional Programming
44mFunctional Programming: Failed Successfully
14mAchieving High-Performance the Functional Way - A Functional Pearl on Expressing High...
59mFunctional Programming for Machine Learning Panel
21mFP for Data Science For Loops Considered Harmful
43mEverything You Always Wanted to Know About Functional Programming...
01h 28mThe Many Paths Towards Functional Programming Language Adoption
57mSome Context for Pure FP Concepts and Style: A Retrospective