Now that we have our view and component layer, we need something to manage state and the lifecycle of our application. Redux is also a clear winner here.
Alongside React, Facebook presented a design pattern for one way data flow called Flux. Flux largely delivered on its promise of simplifying state management, but it also brought with it more questions, such as how to store that state and where to do Ajax requests. To answer those questions, countless frameworks were built on top of the Flux pattern: Fluxible, Reflux, Alt, Flummox, Lux, Nuclear, Fluxxor and many, many more. One Flux-like implementation eventually caught the community’s attention, and for good reasons: Redux.
One thing to be careful is the natural instinct to try and abstract away the Redux boilerplate. There’s good reasons behind all those pieces. Make sure you tried it and understand the “why” before trying to blindly improve on it.
The essentials in order:
- Newbie friendly: Make a Star Wars Game with Hour of Code (free website)
Nobody else has this understanding of the word isomorphic. Words are only useful if they communicate information, but they can only communicate information if we can agree on their definition.
Lots of people think of the mathematical / FP definition borrowed from category theory. An isomorphism is a pair of functions (morphisms) such that: