re: Should I use Redux? VIEW POST


Start without it, but use functions to get shared state. The functions will make transitioning to a state machine easier down the line.

Add redux/some-statemachine when/if the situation starts warranting it.

I love the reducer/redux/flux/(what do we actually call it?) pattern, but I never use it while prototyping.

Also if the implementers dont know functional patterns already, then the learning curve to efficient use is gonna be that much steeper.


Flux is amazing.
I think the structure of separating everything (actions, reducers) in different files has made Redux complex. Otherwise, it's good


I rarely put related code in different files when using redux.

That usually only happens when i hit the ~180 line limit or if i have lots of smaller definitions in it. :)

Code of Conduct Report abuse