What if the user was a function
summary
Argues the user and UI are functions: both map input event streams to output event streams, not blocking calls, so the interaction is a time sequence rather than an array. Shows solving the feedback loop as a fixed point by creating a proxy stream and copying real events back. Decomposes the big "computer" into intent model view functions. Demonstrates code with Cycle.js + virtual-dom and event streams (RxJS), a hello‑name example, error handling via RxJS operators, and component composition.
AI-written summary · about
chapters (7)
related talks
04mUser Interfaces as Pure Functions of Time
43mThe Return of Stream I/O
34mOperate Heavily Dynamic UIs with RxJS
37mStreaming and event-based programming using FRP and RxJS
38mCuring your event processing blues with Rx
35mVisualizing the data flow with Cycle.js
42mConquering Time with Functional Reactive Programming
35mFunctional Reactive Programming with Cycle.js