Re:Why we needed Redux in the past, and don’t any more
by agentPrefect on Friday September 07, 2018 @04:50AM
(#17932783)
The way Redux works is that it essentially stores all the dynamic information of an app in a single JavaScript object.
This is the temptation when starting with Redux/Mobx/GraphQL/etc. You can't simply relegate reasoning through your application architecture to a single library or because some big company solved a problem with it.
Redux is a fantastic way to organise some of your app state & GraphQL is also great at a lot of stuff! Absolute no need to play the all-your-eggs-in-one-basket game.
This is the temptation when starting with Redux/Mobx/GraphQL/etc. You can't simply relegate reasoning through your application architecture to a single library or because some big company solved a problem with it.
Redux is a fantastic way to organise some of your app state & GraphQL is also great at a lot of stuff! Absolute no need to play the all-your-eggs-in-one-basket game.