Go Home (or Skiing) Early: The Joy of Transparent Reactivity
summary
Describes transparent reactivity as a programming model where derived views update automatically to avoid side‑effect bugs and enforce a predictable, deterministic update order. Demonstrates a working “mind reader” demo built on Moldex with a server, showing edits to hundreds or thousands of models propagate in seconds and explaining the minimal data shape (boxes with value and subscribers) and the scheduling that makes it scale.
AI-written summary · about
chapters (18)
- 0:00Introduction
- 1:06Transferring information is hard
- 3:22Joy of transparent reactivity
- 5:12How reactive programming works
- 7:30Problem with manual updates
- 9:14Power of automatic updates
- 10:21Reactive box concept
- 12:27Security in reactive boxes
- 14:35Live demo
- 16:09Building a reactive component
- 17:57Tracking user interactions
- 19:23Small to scalable
- 20:47Complex relationships
- 22:31Moldex dependency tracking
- 24:18Transparent reactivity in practice
- 25:22Moldex differences
- 26:46Update order matters
- 27:28Q&A
