4 ms·
Future fetcher is not a replacement for Redux. It's a feature they will be adding to React later on in 2018 to allow devs to adaptively render elements based on
by chrisco255 9y ago
Future fetcher is not a replacement for Redux. It's a feature they will be adding to React later on in 2018 to allow devs to adaptively render elements based on network performance. You can signal to React to delay rendering specific components until an async operation is complete.
Redux is a state management layer. Future fetching does nothing to solve app-level state management.
Gross misrepresentation of Dan's talk by this article and he made zero mention of the React context API in the talk.
- joshribakoff 9y agohttps://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.