DOM as a Second-class Citizen
summary
Argues that the DOM is an implementation detail, not the end goal, and that React works better when components target the right layer: examples include porting a Link component to react-native, the checkbox bug where setting checked as an attribute fails because the DOM uses attributes for serialization and properties for imperative updates, and shipping layout via a Box tree using CSS Houdini or a browser-side virtual DOM in the browser. Announces renderer extraction (React 0.14) and the push toward universal components and alternative render targets.
AI-written summary · about
chapters (22)
- 0:00Introduction
- 2:14The Basics
- 4:29What is react
- 6:44The Robin Extraction
- 7:02The DOM is our lover
- 7:17The DOM is a terrible target
- 9:20Not all DOM properties are declarative
- 11:17Mashup components can mess with DOM
- 14:07What if we could do something different
- 15:51Virtual DOM
- 17:19CSS
- 19:25CSS Layout
- 21:45React is a Component Model
- 23:30Use Cases
- 24:12Challenge
- 24:45Questions
- 29:20GPU
- 29:37Features
- 34:43Side effects
- 36:39Site loading
- 36:54Whats next
- 37:36Semantic versioning
