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
-
Replying to @stevekrouse
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.
1 reply 0 retweets 4 likes -
Replying to @wcrichton @stevekrouse
cc
@rsnous is that a correct interpretation?2 replies 0 retweets 1 like -
(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
3 replies 2 retweets 30 likes -
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.
1 reply 0 retweets 1 like
More generally, I would love see a systematic breakdown of the "Realtalk ontology" and the different kinds of knowledge/queries you can have. When I've been to DL my learning is always ad hoc from examples, but a more formal system description would be super useful.
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