Concurrent programming seems to be mostly a naming problem.
Was thinking about that, and the paper about PAXOS being fairly straightforward if you define it in terms of immutable registers.
-
-
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.
-
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 more reply
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.