Embrace the "react fatigue"
summary
Claim: react’s tiny core forces many opt‑ins so complexity comes from choices not the topic. Examples: redux and redux‑saga for state and effects, graphql (Apollo/Relay, ETHQL) collocates queries and changes architecture, webpack and CSS‑in‑JS change build and styling, and hooks shrink component code but add new concepts and raise the entry barrier. A blockchain kitten pet project gets built successfully with GraphQL wrappers. Advice: avoid recreating a framework, isolate experiments, prefer opt‑outable stacks or full‑stack frameworks when stability matters.
AI-written summary · about
chapters (25)
- 0:00Intro
- 2:38JS Fatigue
- 7:11A new paradigm !
- 8:30React Fatigue
- 9:59React Frameworks
- 11:35Full-stack Frameworks
- 13:40My experience with webdev
- 14:46Complex project
- 16:51I'm lazy: no opinionation/DSL
- 17:37Add a bit of state management
- 18:30Async / Side-effects in redux
- 18:43redux-saga to the rescue
- 19:22Just moving the problem away
- 19:54Redux ecosystem is huge
- 22:04Composition looks coo.. oh wait
- 26:15Doesn't define how
- 30:31React 16.3: Context API
- 31:41React 16.8: Hooks
- 36:33The bad news: There's no solution!
- 37:04Can be mitigated!
- 40:04Avoid lock-in
- 40:43Every pattern can be dirty
- 41:55Don't go full hipster.
- 43:40Embrace it
- 44:54Stay curious!
related talks
28mThe State of React State in 2019
31mWhy I Still Choose React
30mReact state management in a GraphQL era
50mNavigating the React Ecosystem
40mReact State – The Good, the Bad and the Ugly
28mBack to React: The Story of Two Apps
43mA philosophy of React software design
35mNavigating the Hype Driven Frontend Development World