Can't wait for part 2. I guess one can either make an argument that redux is incomplete or the fact that in large scale applications, redux forces one to write way too much code and makes it easy to cause issues with respect to transitions. We inherently branch out code over time to handle various transitions and FSM approach makes my mind feel at peace.
Regardless, the root cause is with how side effects are handled. And I have loved whatever I have read in this article. Long, but worth the effort. I'm maintaining a large scale application which uses redux-observable to manage side effects and also have to consider state variations across various markets, resulting in a lot of If checks throughout the application. Been looking to implement state machines on top of redux-observable, and I'm not sure that's the right approach. Maybe scratch redux altogether and go all in with state machines and statecharts is another thought, but given its a large app - the thought is scary! Haha.
Again, looking forward to part 2.
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.
Can't wait for part 2. I guess one can either make an argument that redux is incomplete or the fact that in large scale applications, redux forces one to write way too much code and makes it easy to cause issues with respect to transitions. We inherently branch out code over time to handle various transitions and FSM approach makes my mind feel at peace.
Regardless, the root cause is with how side effects are handled. And I have loved whatever I have read in this article. Long, but worth the effort. I'm maintaining a large scale application which uses redux-observable to manage side effects and also have to consider state variations across various markets, resulting in a lot of If checks throughout the application. Been looking to implement state machines on top of redux-observable, and I'm not sure that's the right approach. Maybe scratch redux altogether and go all in with state machines and statecharts is another thought, but given its a large app - the thought is scary! Haha.
Again, looking forward to part 2.