Functional Programming on the Web
summary
Claims that moving from JavaScript patterns to PureScript yields clearer, purer effects and fewer bugs, and demonstrates an actual workflow: compile-to-JS PureScript code, use a foreign-function interface for localStorage and JSON decoders, compose UI with Halogen components and a virtual DOM diff to re-render safely. Includes a concrete UX win—instrumentation shows the default button costing a large number of taxi bookings—plus notes on where promises or FRP became unwieldy and where the build actually works.
AI-written summary · about
chapters (15)
- 0:00Introduction
- 6:00Frontend Development
- 7:27Memory Leaks
- 7:51Too Much Power
- 10:29Lack of Abstraction
- 13:21Giving up responsibility
- 14:04Model View
- 17:37Reactive Programming
- 21:51Elm
- 25:17Functional Programming
- 27:21Pure Function
- 31:01Function Interface
- 33:50Function Effects
- 34:49Arrays
- 35:50Bind
related talks
01h 03mFunctional Programming in JS: What? Why? How?
43mThe Pure Functional Web
01h 03mFunctional Programming in JavaScript
50mIntegrating Purescript and Halogen into Javascript Apps - Part 5 of 6
25mA Guide To Functional Programming
41mFunctional programming: Give it a chance!
43mPure Functional Programming in JavaScript
53mIntegrating Purescript and Halogen into Javascript Apps - Part 1 of 6
