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. :)
Are you sure you want to hide this comment? It will become hidden in your post, but will still be visible via the comment's permalink.
Hide child comments as well
Confirm
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
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. :)