A Reappreciation of Redux
summary
Team at PayPal removed ApolloClient and reintroduces Redux because ApolloClient proves tightly coupled to GraphQL, exposes impure query components, and lacks the explicit reducer/immutability pattern needed for large codebases. Redux gives a pure reducer model, predictable state history and time-traveling devtools that ease debugging; experiments show mixing both creates awkward global state. Hooks promise a future alternative but are alpha then, so Redux wins for durability, clarity, and edge-case handling.
AI-written summary · about
chapters (4)
- 0:00Start
- 4:24Andrew Clark is harsh on Redux
- 7:43We don't know the future of GraphQL at PayPal
- 12:54The essential elements of React are simple
related talks
22mA Reappreciation of Redux: Why my team at PayPal removed Apollo Client and went back to Redux
15mRedux is dead, long live redux!
05mState management in a GraphQL era
29mWrite Queries, Not Code
24mReact State Management In a GraphQL Era
33mMigrating from redux to Apollo
25mRedux is dead, long live Redux!
27mReact State Management In a GraphQL Era