This is a very interesting proposal for handling state management. Are there any expected benefits from this approach versus Redux? Besides allowing the teams to get comfortable with GraphQL.
Also, with hook and concurrent mode coming it seems like more optimized and performant solutions than Redux would emerge. Specifically I am thinking of having a state management solution for the global application state pieces, but then the state that is only shared inside of modules could be handled with useReducer and ContextAPI.
It sounds like Apollo is looking to improve upon this existing solution to make state management even easier and more robust. With that said, several folks in that thread make great points about why this may not be the best approach.
Still an interesting exercise and I'm glad it started a conversation.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
This is a very interesting proposal for handling state management. Are there any expected benefits from this approach versus Redux? Besides allowing the teams to get comfortable with GraphQL.
Also, with hook and concurrent mode coming it seems like more optimized and performant solutions than Redux would emerge. Specifically I am thinking of having a state management solution for the global application state pieces, but then the state that is only shared inside of modules could be handled with useReducer and ContextAPI.
Thanks. Great questions which were addressed a bit in this thread: twitter.com/swyx/status/1166733744...
It sounds like Apollo is looking to improve upon this existing solution to make state management even easier and more robust. With that said, several folks in that thread make great points about why this may not be the best approach.
Still an interesting exercise and I'm glad it started a conversation.