Strict DOM
summary
Vision argues for unifying web and native by mapping web APIs to native and shipping a prototype called React Strict DOM that exports HTML and CSS modules. It uses codemods and a Stylex/StyleSheet-compatible style system to migrate existing web code quickly, reusing complex features; one Meta app shares 60% of files and React Strict renders 10% of divs and 20% of spans on facebook.com. About 63% of target web APIs are supported, native polyfills make a div about half as fast as a view, and overall native DOM performance improves ~2.5× with ongoing work.
AI-written summary · about
chapters (10)
- 0:00Introduction to Strict DOM
- 3:37Current React fragmentation
- 6:46React Strict DOM vision
- 8:31How React Strict DOM works
- 10:38Native web API convergence
- 12:42Code migration and performance
- 13:48Real-world example Facebook VR
- 15:37Trade-offs and future goals
- 18:05Three goals for React Strict DOM
- 19:28Call to action and conclusion
related talks
40mDOM as a Second-class Citizen
36mHorror Stories From Hacking the DOM Into a Native Platform
34mWhy we need a better browser
30mReact: Rethinking best practices
31mNative Web Components - All Frameworks Invited
51mFunctional Web Development – An Introduction to React.js
21mBuilding Cross-Platform Component Libraries for Web and Native with React
36mThe Road to Native Web Components
