The work that you don't see
summary
The claim is that boring infrastructure work is what actually restores trust in React Native and it gives concrete results not platitudes: changelogs generated through a tool and published release documentation remove bus factor, a release crew with two community and two Meta engineers rotates work, npm adoption metrics show version 0.71 surpassing 50 percent and upgrades smoothing, and a year‑long effort to consolidate packages yields monorepo consolidation and automated package releases with 0.72 as the first version in the new configuration
AI-written summary · about
chapters (10)
- 0:00Introduction
- 1:50React Native disaster recipe
- 6:48Boring work in open source
- 7:29Releases and hidden improvements
- 12:22React Native releases evolution
- 14:07Monorepo impact
- 16:14Open communication in React Native
- 17:59Contributing to React Native
- 19:46Microsoft’s React Native role
- 20:27Key takeaways and trust
related talks
22mThe 1.0 is a lie: The complexities of releasing React Native
25mReact Native in Practice
27m22 - A year in Review for React Native
34mChanging React Native... from within!
38mThe Power Of Process Automation
10mGreenfield of Dreams
27mBringing the New React Native Architecture to the OSS community
29mA practical approach to building truly native cross-platform applications at scale