It is in fact designed to make it simpler. Handling state gets very complex very quickly. This problem scales with the size of an application. Redux lets us control state, to minimise it, and to manage it within a subset of the language. This ultimately makes it easier to reason about.
Junior devs may not pickup Redux straight away but I'm not entirely sure they should. Making something easy to understand in order to appeal to the lowest common denominator in terms on language experience doesn't really seem like a long term plan for building reliable applications.
On a personal level I actually think that redux is easy enough to learn, the problems are that people think it's for something it isn't (injecting props arbitrarily throughout a component tree) and that the concepts (immutable state, functional patterns) are so alien to people that they have a hard time moving past them to understanding the overriding concepts.
Passionate generalist conquering the web one project at a time. Whether authoring libraries for node, JS, PHP, or Rust, I am always on the lookout for better solutions to common problems.
Location
USA
Work
Lead Developer & Co-founder at corpscrypt, CTO at REtech
Making something easy to understand in order to appeal to the lowest common denominator in terms on language experience doesn't really seem like a long term plan for building reliable applications.
I agree with that. But that doesn't mean I can't derive the conclusion that if something has a huge learning curve and maintenance cost it might not be an ideal solution.
This certainly does not mean that I want to advocate for a passing down props/callbacks a gazillion levels and bubbling events up to grandparent's parents.
What I am saying is: I remember the feeling of being surprised that there isn't a better solution. And I am not alone with this. My approach for VueJS is a concept known to React devs from recoil
I didn't actually mean to disagree or pick holes in your original post, sorry if it came across that way. I just see a lot of people complaining about using Redux because it's a heavy-weight way to inject props, which seems slightly unfair to me.
I'm all for anyone advocating any approach that they've at least slightly thought through, so good luck to you with this approach.
Passionate generalist conquering the web one project at a time. Whether authoring libraries for node, JS, PHP, or Rust, I am always on the lookout for better solutions to common problems.
Location
USA
Work
Lead Developer & Co-founder at corpscrypt, CTO at REtech
Sorry, let me rephrase, I was wrong to say:
It is in fact designed to make it simpler. Handling state gets very complex very quickly. This problem scales with the size of an application. Redux lets us control state, to minimise it, and to manage it within a subset of the language. This ultimately makes it easier to reason about.
Junior devs may not pickup Redux straight away but I'm not entirely sure they should. Making something easy to understand in order to appeal to the lowest common denominator in terms on language experience doesn't really seem like a long term plan for building reliable applications.
On a personal level I actually think that redux is easy enough to learn, the problems are that people think it's for something it isn't (injecting props arbitrarily throughout a component tree) and that the concepts (immutable state, functional patterns) are so alien to people that they have a hard time moving past them to understanding the overriding concepts.
I agree with that. But that doesn't mean I can't derive the conclusion that if something has a huge learning curve and maintenance cost it might not be an ideal solution.
This certainly does not mean that I want to advocate for a passing down props/callbacks a gazillion levels and bubbling events up to grandparent's parents.
What I am saying is: I remember the feeling of being surprised that there isn't a better solution. And I am not alone with this. My approach for VueJS is a concept known to React devs from recoil
I didn't actually mean to disagree or pick holes in your original post, sorry if it came across that way. I just see a lot of people complaining about using Redux because it's a heavy-weight way to inject props, which seems slightly unfair to me.
I'm all for anyone advocating any approach that they've at least slightly thought through, so good luck to you with this approach.
Oh, don't worry, I didn't take it that way.