Why I Still Choose React
summary
Argues for React because its core claim — that UI is a function of state — still yields predictable composition and ten years of real-world experience. Calls out Hooks' promise of 90% cleaner code but shows the surprising 10% of cases where instantiation, DOM-only APIs and SSR force convoluted workarounds and useEffect spaghetti (double runs in React 18 StrictMode, refs, cleanup mysteries). Compares Solid’s signals and how conditionals require new APIs, and notes an experimental compile-time approach React Forget as a potential non-invasive solution.
AI-written summary · about
chapters (9)
- 0:00Introduction
- 3:39Why React in 2023
- 5:03React’s original promise
- 10:45Hooks and React development
- 17:53Hooks and effects challenges
- 18:57Alternatives like signals
- 24:18React’s future and mental model
- 29:36React’s composition model
- 30:18Closing
related talks
28mThe State of React State in 2019
45mWhy I am hooked on the future of React
50mNavigating the React Ecosystem
01h 04mWhat makes React different?
36mReusing Stateful Logic in React: HOC vs Render Props vs Hooks
20mReact Realism: Is there another alternative?
40mReact State – The Good, the Bad and the Ugly
27mHooked on React Hooks