React vs. The Rest of The Web: Civil War
summary
Builds the same RSS-like app across 10 frameworks and shows code differences: React reexecutes each functional component top-to-bottom on rerender and forces memorization with hooks; signals update only subscribed DOM nodes so components don’t rerender; Angular moves fetching into services and exposes Observables to templates; compiler frameworks ship reactive stores that update HTML nodes directly; vanilla JavaScript version proves the app works with plain DOM manipulation and event listeners.
AI-written summary · about
chapters (12)
- 0:00React’s perceived decline
- 1:05Comparing React with others
- 3:37React rendering and state
- 7:37Preact: hooks to signals
- 11:34Angular’s class and observables
- 15:28Signals vs observables
- 17:34Svelte’s compiler reactivity
- 20:50Solid’s signal reactivity
- 23:20Choosing a framework
- 26:33Vanilla JavaScript alternative
- 29:50Speaker and resources
- 30:36Q&A
related talks
30mReact: Rethinking best practices
58mFrontin' like a Back-er
51mDeep dive into modern frameworks Reactivity🔬⚛️
11mReactivity as Catalyst: Driving Evolution in React, Vue & Angular
21mUnderstanding Rendering Patterns
33mReactJS as the MVC
49mA comparison of the Reactivity Concepts in Angular, React, Vue and Svelte
44mComparative study of reactivity across frameworks and implications for Resumability