Recent searches
Search options
So it's 2010. The Haskell users are telling me, state is bad. State creates headaches. Instead of having mutable state in your app, pass around values to and from functions. I ignore this.
It's 2024. I now use Rust, which makes mutable state real hard. I decide to finally take the Haskeller advice. And… I find I'm still having state headaches, but now the state is wiggling spaghetti moving all over my code instead of being in one single variable where I can easily keep an eye on it
@mcc Regarding the state, honestly, part of the thing is just to get used to having everything as argument. In the #react world (where I had the misfortune of working) they added a special mechanism to prevent the need to pass the state manually, which IMO worked way worse than just passing the state manually.