Human React
summary
Argues that React’s value is human outcomes not clever APIs: accessibility, internationalisation and web performance are treated as concrete requirements (maps must work on 2G, a 300‑test suite means nothing if UX buttons mislabel), and ethical stakes can be literal (life‑critical routing). Recommends prioritising accessibility is human rights, avoids pointless tech fetishism (don’t ship Moment.js), jokes about desux and urges teams to fix accessibility before refactoring to Hooks.
AI-written summary · about
chapters (6)
- 0:00Start
- 6:57Why Did You Choose React
- 9:22Why Should You Choose React
- 12:16Thought Experiment
- 20:21Accessibility
- 21:53When Should You Refactor Your App to Two Hooks
related talks
31mWhy I Still Choose React
49mSupporting accessibility in React: the difficulties and niceties
50mNavigating the React Ecosystem
34mBuilding Accessible Web Apps in React
23mWorse is Better: The Upside of JavaScript Fatigue
41mDemystifying Accessibility in React Apps
29mStyling React For Reuse
28mRequisite React
