News for hackers. Stuff that matters.
Re:A General Theory of Reactivity by seanmcdirmid on Saturday March 21, 2015 @07:29PM (#9244706)
It seems to be more about ideology than theory, but theory is as overused as "reactive."

React is a good example of a framework that lies outside of this: it is a simple solution for the problem that doesn't involve callbacks, promises, or even observables. My own project, Glitch, solves these problems by managing time:

http://research.microsoft.com/en-us/people/smcdirm/managedti...

It doesn't block, it doesn't use functional abstractions either, Glitch simply replays code until all writes have seen all reads (it also doesn't requiring lifting of time-dependent values in the same way that React doesn't). Also, see:

http://research.microsoft.com/pubs/230746/control.pdf

Which argues that we might have given up on control flow too soon.

Still this isn't a bad essay for what it is, even if it isn't very general.

Re:A General Theory of Reactivity by pron on Saturday March 21, 2015 @07:37PM (#9244737)
Those papers relate to real reactive programming (aka dataflow); the article discusses something else entirely, namely ways to write concurrent, low-latency, responsive applications. Unfortunately, it picks the more cumbersome approaches to achieve that goal.
Re:A General Theory of Reactivity by seanmcdirmid on Saturday March 21, 2015 @07:41PM (#9244745)
Ya, it is more systems than PL. See my reply to your other comment.
Re:A General Theory of Reactivity by cowbertvonmoo on Friday March 27, 2015 @07:47PM (#9279785)
You are absolutely right that React accomplishes much without discrete event-driven change propagation. React falls clearly under the "behavior" style of reactivity, meaning that the state is polled to effect change. This is particularly useful in situations where change occurs more frequently than rendering, or even continuously.

I talk about this toward the end of GToR.