The New Best Practices
summary
React’s big claim is that components are a single, composable primitive that power long-term innovation; five years after 2013 that still holds. Concrete tools mentioned: Apollo integrates by wrapping with a higher‑order component, Storybook catalogs UI, jscodeshift automates deprecations, and Flow/TypeScript/Reason add machine‑checked docs. Important surprises: Suspense lets render throw promises so render methods are not strictly pure. Rules that prove useful: build big from small, write for humans, prefer simple solutions, and avoid breaking consumers.
AI-written summary · about
chapters (17)
- 0:00Introduction
- 1:50React
- 5:05The Problem
- 6:20Innovation
- 9:50Framework Wars
- 11:55Components
- 12:37React Components
- 17:15Best Practices
- 18:17What about suspense
- 20:13What we need
- 21:47Title
- 22:45Rule 1 Build big things
- 23:52Rule 2 Write code for humans
- 24:55Rule 3 Use primitives
- 26:11Rule 4 Use simple solutions
- 27:08Rule 5 Dont break things
- 28:37Rule 6 Open mind
related talks
44mWriting good components
52mBuilding Modern React Applications
44mA Practical Guide for Crafting Resilient UI Components
33mBuilding modern React applications
23mBest Practices for reusable UI components
38mState of React
15mReact Best Practices in 15 Slides
50mWriting React Components: The Functional Way