Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

When to use redux #136

Open
blocka opened this issue Nov 27, 2016 · 0 comments
Open

When to use redux #136

blocka opened this issue Nov 27, 2016 · 0 comments

Comments

@blocka
Copy link

blocka commented Nov 27, 2016

I see that you write a lot on when not to use redux, especially in the context of blindly replacing setState with redux for now apparent gain (ie., glorified setters). Understandably, there is not much added architecturally except for indirect, boilerplate and noise.

Can we say that, even in that case, redux gives us other advantages? For example, time-travel debugging, ecosystem, ability to use tools such as redux-saga for elegantly dealing with side-effects and async programming, in general, clear architectural rules (ie., easier on-boarding), easily serializing state and action log, etc.

It seems there are a lot of advantages in using redux outside a todo app, or calculator, even if the reducers do become "glorified setters".

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant