There is nothing about these that make them related to "general reactivity", mostly because there is no such thing as reactivity. They are simply techniques of performing actions in referentially transparent languages. In imperative languages, the most general, theoretically pure, fundamental construct of "reactivity" (whatever that means), is the thread (Erlang's send is not special, and not required).
There is absolutely nothing more fundamental about the referentially-transparent (lambda calculus) way of doing things than the imperative way of doing things, and since the article discusses imperative languages, the LC way of doing things is potentially harmful as there is nothing to enforce referential transparency.
And those things GTOR does use in square 1 are fine. Your heavyhanded rejection of them is colosssaly sad and twisted. If a mental construct suits a problem and helps you think of it, that's what is important. The programmatic platform follows our ability to think, it does not define it, yet you keep insisting the cart must come first, that the platform has to be a certain way or else or else or else. FUD. FUD FUD FUD.
It's using the references that everyone on the planet but those of your little cultish view know to explain general ways of thinking about things. Your unwillingness to see parity between the general ideas put forward because it's not your favored implementation reads grossly to me. Observers, contracts, data-flow are real, graspable concepts and if they closely model how you want to think about a problem then they are most definitely good concepts, and it's up to the platform to have good ways to express natural thought. I still have an enormously hard time decyphering the mad mess of shibboleths you toss out, activating your elitist trope of true beleievers (and I'm not a complete neophyte to your clique myself), but I am 100% sure, as I stated in my first paragraph, that all systems enact a coupling/reactivity. Control, whether it's explicit or implicit in the flow, is still the chief thing entailed in mentally modeling and putting into practice: this is unrejectable.
In particular, your bringing up of the referential transparency doubles down on my prime criticism in the previous: you bring up points that you claim contend, but you provide no support, no structure where anyone but those already attuned to your brand of thought can get onboard with you. Your claims are uncontestable, because they are indecypherable. They claim a split, but don't deign to point out what that split is. That, culturally, is a big indicator to me.
Your case rests around whether or not reactivity is a general thing or not, and I think it's quite clear we can find these concepts embodied in any system.
What is "reactivity"? This document defines it as "the process of receiving external stimuli and propagating events". Ok, then -- I wouldn't call it a very rigorous definition, but I can roughly grasp what the author means (more or less; I think). Now, please show me why callbacks, promises or observables are more "general" approaches to "reactivity" than, say, threads, blocking queues and blocking futures? I chose those because they happen to be the duals of the aforementioned constructs. If A is a dual of B, how can you say A is the "general theory" while B is a "cultish view"? This is what is very much rejectable.
Now that we've firmly established that A (callbacks, promises, observables) is no more general than B (threads, futures and queues) -- yet the document focuses on one while completely ignoring the other -- I express my opinion (that I can support[1]), which is that in imperative languages, constructs B are far superior to their no-more-general constructs A. That, however, unlike my previous statement (about the document confusing goals with implementations, which was a statement of fact), is just a statement of opinion.
> Observers, contracts, data-flow are real, graspable concepts and if they closely model how you want to think about a problem then they are most definitely good concepts, and it's up to the platform to have good ways to express natural thought.
Sure they are, but this document mentions some antipatterns to implementing these abstractions (which is why I said it confuses implementation with abstraction). Queues are definitely a dual of observables, and in my (and many others') opinion, they are a far superior way of implementing dataflows in imperative languages (they provide implicit backpressure, and they make concurrency clear). Same goes for futures vs callbacks, or threads vs monadic composition (threads preserve stack traces, control flow and exceptions, while monads/promises don't -- they require a shadow implementation of all those basic constructs).
I model many problems with a dataflow abstraction, but when I want to implement it, I reach for a blocking queue (aka, channel) rather than observables. Don't confuse abstraction with implementation.
[1]: https://www.usenix.org/legacy/events/hotos03/tech/full_paper...
I agree with grand parent on this one. Since it "complects" what is to be done with how to do it, it's by definition not as general as it could be.
Are you getting hung up on the fact that GTOR talks through some specific apis for reactivity? You seem very much opposed to letting someone mention callbacks, prormises or observability? But GTOR is itself about mentioning these things so we can get past them and think of reactivity more generally. Yet you seem mired in your hatred for these concepts, in a way that prevents you from seeing that the article is about building effectful processing- having code or data whose effect is the running of other code, in a general fashion. And your inability to see that generalness, your forcing some weird diatribe against non-greenthreaded systems as all missing the point, is there rooted itself in confusing an implementation with intent, for surely blocking or no, concurrent or non, code and data will create reactions amid others.
I suggest getting more into the categories about. Sometimes binding happens before event, sometimes event before looking. Sometimes event is singular, sometimes it's over a duration, sometimes it's ongoing- edge, level triggering and continuous. Sometimes event has concurrency sometimes it's over time.
None of these don't make sense in Erlang or any other runtime, even if you might not see them expressed as first class constructs with apis, even if the reactivity were more baked in, as Erlangs send is.
Most of all, I have a very hard time understanding what your clash really is. I feel very much I'm being sold something, but the first paragraph doesn't give me a clear idea of what it is I'm being asked to accept evidence for.