The Front End Architecture Revolution
summary
Argues that combining React, immutable data structures, and server-side graph queries (Relay/GraphQL or Netflix Falcor) cuts client complexity and networking: 40M-page-election traffic example and a pixel editor (≈2,000 lines) implements infinite undo in 60 lines using persistent data. Recommends Transit for efficient rich-data transport, ClosureScript + Google Closure for whole-program optimizations, and Datomic-style recursive pulls to eliminate ad hoc REST reshaping and enable single-request batching and global performance wins.
AI-written summary · about
chapters (27)
- 0:00Intro
- 4:30Simplicity
- 9:14Global Optimization
- 10:18Garbage Collection
- 10:54React
- 13:04The Big Idea
- 13:16The Benefits
- 14:46Backbone
- 16:08React JavaScript
- 16:58Algorithms Matter
- 17:37Persistent Data Structures
- 19:18All the code
- 19:57Which language
- 21:39Google Closure
- 22:15Closure Script
- 23:38Closure Compiler
- 25:56Moving Data
- 26:11Transit
- 28:16Cache
- 29:29Meteor
- 30:26React Relay
- 31:25Falkor
- 32:31Big Ideas
- 33:43Concrete Example
- 33:56Atomic
- 34:10Pull
- 36:31Radical Simplicity
related talks
58mFrontin' like a Back-er
24mRethinking frontend architectures with data layers
30mMicro Frontends in React — a State of the Art Approach
27mThe Functional Final Frontier
40mReactive Programming: A Better Way To Write Frontend Applications
30mReact: Rethinking best practices
31mReimagining the frontend-backend divide thanks to GraphQL
38mThe challenges and benefits of a functional reactive frontend