Concurrent programming seems to be mostly a naming problem.
-
-
-
Replying to @chatur_shalabh
I had just been reading about CRDTs for realtime text editing. A central challenge seems to be to name things, and parts of things, that allow others to know what you're talking about despite having a different picture of the world.
1 reply 0 retweets 0 likes -
Replying to @peidran @chatur_shalabh
Was thinking about that, and the paper about PAXOS being fairly straightforward if you define it in terms of immutable registers.
1 reply 0 retweets 0 likes -
Replying to @peidran @chatur_shalabh
It just seemed like a lot of problems in concurrent (and regular?) programming come down to using a single name for things that change over time. A strategy for concurrent programming is to providing facts, or observations, and weaving them into a story at query time.
1 reply 1 retweet 2 likes -
Replying to @peidran
Yes, change over time and also change across location. Related I found David Reed's NAMOS (1978) interesting. "Synchronization can then be treated as a mechanism for naming versions to be read." I wish more languages and systems had built-in support for versioning its objects.
1 reply 0 retweets 1 like
It’ll be a core (non-optional) part of what I’m building, but I’m not trying to support general purpose programming.
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.