Navigating the Hype Driven Frontend Development World
summary
Claims that hooks boost team productivity but hooks are not a global state solution and require memoization to avoid excess renders; compares Redux (verbose), MobX (magic rerenders, heavier bundle), and Overmind (small, TS‑first). Gives a concrete win: Apollo’s client.resetStore replaces complex per‑mutation cache updates and client.resetStore replaced weeks of cache work. Mentions building a browser for designers (cz) and argues shipping paid products beats chasing GitHub stars.
AI-written summary · about
chapters (9)
- 0:00Start
- 1:08Hooks are not
- 2:46Have a global store
- 2:57Provide store
- 3:38Bonus
- 5:56Overmind
- 6:30Hi, I'm Kitze @thekitze
- 6:45sizzy.co The browser for designers and developers
- 34:29Stop seeking external approval Stop seeking answers in other people's projects
related talks
34mNavigating the Hype-Driven Frontend Development World Without Going Insane
24mHooks, HOCS, and Tradeoffs (⚡️)
17mReact hooks: the good, the bad and the ugly
30mReact state management in a GraphQL era
22mGoing beyond Redux. Diversify frontend state management
28mUnpopular Opinions
35mHandling Large-Scale State Management with Context and Hooks
18mDestructuring state management (in React)