4 ms·
Ah, yes. That paper (among other things) inspired me to implement true lightweight threads on the JVM. I also use some of the arguments in that paper to demonst
by pron 12y ago
Ah, yes. That paper (among other things) inspired me to implement true lightweight threads on the JVM. I also use some of the arguments in that paper to demonstrate that while pull and push are technically duals, in practice, pull APIs are always superior (except, again, in referentially transparent languages that lack the concept of a stack and a thread).
- seanmcdirmid 12y agoI've been writing.designing reactive programming languages and frameworks for more than 10 years now, I started out with Superglue in my dissertation: http://lampwww.epfl.ch/~mcdirmid/papers/mcdirmid06superglue.pdf http://lampwww.epfl.ch/~mcdirmid/papers/mcdirmid06superglue.... Early on, I realized that pull was the only safe/sane solution, so in all my languages (barring early versions of Superglue), change propagation merely dirties execution that could have read the changed value, which is queued to be re-executed and will pull the new value if it still depends on it. That is the style that I use for Glitch, and it has turned out to be very robust. Push is much harder. Actually, I'm not even sure how those systems even work properly; too many things to coordinate.