Tyler McGinnis - Why React Hooks?
summary
Explains why Hooks replace classes by naming the actual primitives: useState returns [value, setValue] to add local state in functions, useEffect centralizes side effects so fetching logic no longer lives in multiple lifecycle methods, and custom hooks like useRepos returning [loading, repos] let non-visual logic be reused across components. Calls out concrete wins: no more super/this binding, less duplicated sync code, functions instead of class boilerplate, and simple composition that actually works for data fetching and state handling.
AI-written summary · about
chapters (11)
- 0:00Start
- 2:17June 14, 1998
- 2:44May 29, 2013
- 4:39constructor
- 5:13Autobinding
- 5:54Class Fields
- 6:53Duplicate Logic
- 7:37Sharing non-visual logic
- 8:41Feb 11, 2015
- 11:20Current State
- 16:17Custom Hooks
