We all know mutable state can be problematic. But the explanations tend to be abstractions like "reasoning" and "composability". What's a simple *convincing* example in single-threaded code? Having trouble making one that isn't obviously bogus. Is it only a problem at scale?
-
-
My reading is their examples don't show actual *problems* with imperative code. They just show how more *beautiful* the functional code is.
-
I think Backus' comparison provides reasonable arguments for the functional version that don't appeal to aesthetic. He argues about nameless-ness, compositionality, generality.pic.twitter.com/b2tpuYT4SZ
- Show replies
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
cognitive psychology. PhD