4 ms·
https://dev-blog.apollodata.com/the-future-of-state-management-dd410864cae2 https://dev-blog.apollodata.com/the-future-of-state-manageme... What about apollo-l
by joshribakoff 9y ago
https://dev-blog.apollodata.com/the-future-of-state-management-dd410864cae2 https://dev-blog.apollodata.com/the-future-of-state-manageme...
What about apollo-link-state? Not a replacement either per se, but seems like its one step closer to isomorphic (client & server side) state.
On one hand it normalizes your data & avoids thousands of lines of boilerplate, on the other hand you lose [some] control of the underlying data structures which is where you'd still need something like redux.
- chrisco255 9y agoI love Apollo. I think it's great! It really does reduce like 2/3 of the state you need to manage in your app. Only caveat is that it's somewhat arduous to use unless you have a GraphQL backend, so you really do have to buy in to that whole stack. That's sometimes a luxury not all products/teams are blessed with.