Re:Explicit State Machines in React
by runawaybottle on Monday May 25, 2020 @04:09PM
(#23304434)
Well, do write the dense blog post because it acts as something more substantial for surveyors who may not put more thought into it other than ‘I guess this and stuff like Redux is how to do web apps now’. Usage of these patterns is not an insignificant decision without trade offs, and by no means right for every app. I can similarly make a case that some of the features you outlined for tweets could be done in a sensible intuitive way that doesn’t introduce an explicit state machine.
I’ll leave a good dense article on developer friendliness of some of these apis that you may want to address as well, since a larger symptom of the architecture you suggest is boilerplate:
https://christianalfoni.com/articles/taking-immer-one-step-f...
Re:Explicit State Machines in React
by daneburkland on Monday May 25, 2020 @04:41PM
(#23304742)
Agreed! Always trade offs. Will give that a read. Thanks again.
Thanks for the feedback. The benefits of modeling application logic with state machines are increasingly apparent as complexity grows. But that complexity makes for a dense blog post :)