AMA with Michel Weststrate
summary
AMA session moderated by Gerard Sans dives into specifics: Apollo local state feels premature for derived computed data, React context does not replace state libs, and using both Apollo and Redux can be overkill; MobX makes components automatically smart via observer, plans include decorators and adopting hooks, and trace helps map mutations to renders. Debugging favors the JS debugger with conditional breakpoints over console.log. Open source guidance stresses clear scope, test coverage, minimal reproducible issues, and empowering contributors.
AI-written summary · about
chapters (5)
- 0:00Start
- 0:27The Different Approaches to State Management
- 3:30Separate Your Ui from Your State
- 11:09What Are the New Features in the Latest Versions of Molex
- 16:19Do You Think the React Context App Api Has Removed the Need for Additional State Management Libraries in React
related talks
24mPanel discussion hosted by the Apollo team on GraphQL + React
42mQ&A Panel with Core team and speakers
24mPanel discussion about state management
25mReact state management in a GraphQL era
24mReact State Management In a GraphQL Era
24mState Management in React Apps with Apollo Client
22mReact State Management in a GraphQL Era
30mReact state management in a GraphQL era