Controlling Time and Space: understanding the many formulations of FRP
summary
Clear claim: FRP splits into concrete designs with tradeoffs — Elm's static signal graphs (signals tied to the world, synchronous, efficient), higher‑order FRP (join needs unbounded history unless types restrict it), asynchronous/reactive systems (hot/cold streams, no referential guarantees), and arrow/automaton FRP (detach from world). Tools and demos: Elm primitives (foldp, lift — lift stops at eight), integration with Rx/Bacon, and a working demo of hot‑swapping and the Time Traveling Debugger showing code edits and rewind that actually work.
AI-written summary · about
chapters (11)
- 0:00Start
- 2:14Inputs
- 3:02Transformations
- 3:58State
- 4:53Merge
- 6:18First-order FRP "How it works in Elm"
- 13:58Higher-order FRP
- 15:31Example
- 21:05Asynchronous Data Flow
- 25:52Dynamic Collections
- 33:30Controlling Time and Space
related talks
45mFunctional Reactive Programming in Elm
29mRethinking All Practices "Building Applications in Elm"
50mIntroduction to Reactive Programming
56mSimplifying Web App Development With Elm and Functional Programming
38mConfident Frontend with Elm
34mAMA - Richard Feldman
46mFRP with Bacon.js
01h 28mFunctional Programming for the Web with Elm