A Skeptic's Guide to Functional Style Javascript
summary
Argues that functional style in JavaScript is practical not purity dogma: prefer small composable units, name functions, and use array methods instead of manual loops so code becomes easier to reason about and test. Demonstrates replacing for loops with map/reduce/filter and using closures and currying for event handlers. Calls out that side effects and mutability still happen and that promises act like monads. Recommends tooling to help: Ramda and Immutable.js for common helpers and safer immutable data.
AI-written summary · about
chapters (15)
- 0:00Start
- 0:10#functionalStyleJS SKEPTICS GUIDE TO FUNCTIONAL STYLE JAVASCRIP
- 3:23What is Functional Programming?
- 4:18that treats computation as the evaluation of mathematical functions
- 8:54Side effects are evil!
- 15:09Let's look at arrays
- 17:58What are we doing?
- 18:24We need a pure function
- 20:25Why pure functions?
- 25:17Why Immutability?
- 28:36Chain functions FTW
- 33:36Currying
- 44:35It is the tooling that does the work...
- 45:02Simplify the pieces
- 45:50Keep the interactions simple
related talks
45mA Skeptics guide to functional style javascript
49mA Skeptics guide to functional style javascript
20mFunctional JavaScript
25mA Guide To Functional Programming
53mMaintainable JavaScript with Functional Patterns
34mFunctional JavaScript for everyone
51mWhat the Functional? What, How and Why
12mAn introduction to functional programming