And congrats on completing the reactor's part of the course, next on our list, redux, unlike reactors
redux is not part of official reactor.
Of course, since it's used so often in REAC project, one might think that it's part of reactor, but
in fact, it's not.
In short, Redux is an up level state management library.
I know, I know.
Sounds extremely complicated.
But keep in mind that we are already familiar with Apple.
Remember context.
Well, in a lot of ways, redux is very similar to context here, just a bit more rigid and opinionated.
In fact, if you're comfortable with use, reduce or hook, I can guarantee you you'll grasp the main
concepts of redux in no time.
The main idea of redux is exactly the same as for the context, the setting up of the state in the app
level.
So multiple components have access to the state and as a result we can avoid Parap drilling or passing
down the props through the components that actually don't need them.
We purposely cover Riddick's at the very end of the course.
For one, despite common misconception, you don't need to use redux in all your react projects with
arrival of context API reactants and user Doozer in particular.
Only very big project might require redox.
So please don't start converting all your projects to Redux, despite what the Twitter gurus might tell
you.
And the second reason why recovery works at the very end is because even though Redhawks is not hard
and the actual API is quite small, it is my strong belief that you'll understand it way faster and
better once you have a solid understanding of main reactor concepts.
Since there's not much theory to cover about Redox, we will directly proceed to build a project using
Redux, and I purposely picked one of the projects we already completed previously.
Since that way we can focus on redox implementation only and avoid wasting our time on irrelevant details.