Next generation of frontend architectures
summary
Reactive frontend claims move from callbacks to data flows: MVI enforces MVI unidirectional flow where intent maps DOM events, model holds state and view emits a virtual DOM. Implementation uses RxJS streams (engine emits numbers every 3s for a Bingo of 40 numbers in Bingo with two 15‑number tickets; shareReplay/buffers backfill new tickets) and Cycle.js (app.run with drivers, ~100 lines). Live Tube demo polls Open Data by combining interval and HTTP streams; result is less global state and easier debugging.
AI-written summary · about
chapters (6)
- 0:00Start
- 1:00Architectures Timeline
- 7:24PROGRAMMING PARADIGMS
- 18:35OBSERVER PATTERN
- 22:18MVI RULES
- 33:28Cycle.js
related talks
44mThe evolution of frontend architectures
40mReactive Programming: A Better Way To Write Frontend Applications
36mRxJS: A Better Way to Write Frontend Applications
35mModel View Intent, Embracing Reactive UI's
34mEffective Reactive Architecture
45mHow to Manage Your UI State: Virtual DOM and RxJS
28mReactive all the Things
35mFunctional Reactive Programming with Cycle.js
