You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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".
The text was updated successfully, but these errors were encountered:
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".
The text was updated successfully, but these errors were encountered: