cognitive psychology. PhD 
In trying to convince others that *global mutable state* is a bad idea, I realize I don't have any hard evidence - just abstract reasons. At the very least, I'd like an illustrative code example I could point to. Any suggestions?
Show this thread
-
Dynamicland would arguably refute this. The entire programming model is having one giant blob of global mutable state, the Realtalk database, and programs are small functional modifications to the db with built in semantics to manage conflicts.
-
-
Omar and I actually debate this very point when I interviewed him on the podcast. Part of the reason it works at Dynamicland is that the code is supposed to be really small. Just a couple pages on a table
-
Yeah, close -- I haven't thought about this but believe it's not 100% the same as imperative mutable state You can _add_ state (make new Claim) and react to it in the same tick, but you can't mutate it in place until the next tick. Something like React or register-transfer level
- Show replies
New conversation -
-
-
(btw, thank you for provoking this -- it's helpful as I'm preparing to write up Realtalk and need to understand the misconceptions that need to be addressed)pic.twitter.com/wBGRVCyZAH
-
Thanks for the clarifications! Does the query model ("when /a/ is a frog") permit use of knowledge about the claimer ("when /b/ is on same table as /a/, /b/ is claiming /a/ is a frog")? Seems important in distinguishing knowledge sources.
- 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.