Cofounded Host Collective (DiscountASP.net). Cofounded Player Axis (Social Gaming). Computer Scientist and Technology Evangelist with 20+ years of experience with JavaScript!
The state monad is a lazy state manager. I could see it being useful when passing to functions as they would lazily update the state. The state wouldn't then be computed until you need to compute it, which wouldn't happen inside of the pure function.
It's also nice that it returns the computed value and the state as a pair. I feel like this could be useful, but I haven't really thought of a good use case for it yet.
I have read a bunch of stuff on the state monad and don't understand any of it.
The only thing I did understand was this, which might also be helpful to you:
Could you explain the state monad for me?
Not well. I have never used it.
The state monad is a lazy state manager. I could see it being useful when passing to functions as they would lazily update the state. The state wouldn't then be computed until you need to compute it, which wouldn't happen inside of the pure function.
It's also nice that it returns the computed value and the state as a pair. I feel like this could be useful, but I haven't really thought of a good use case for it yet.
I have read a bunch of stuff on the state monad and don't understand any of it.
The only thing I did understand was this, which might also be helpful to you:
State Monad in JavaScript
I'm not so much of a stickler for this level of purity and algebraic state management. When I need state, I'll usually grab redux.
I would compare it to a be redux reducer.
Cheers!