This is an interesting article, but I don't think it gives enough credit to Functional Programming. The article presents functional programming applied to push

This is an interesting article, but I don't think it gives enough credit to Functional Programming. The article presents functional programming applied to push streams, which is part of FRP but only one way to look at Reactive Programming. Thinking in streams is a great exercise but is not a panacea. It's really easy to get started with streams in a toy example, but in real world applications backpressure and buffering are a concern. The consideration of backpressure also opens the push/pull stream discussion. If you are interested in applying more from this article, the API is very similar in Godot2 (Node) [0], which is based on Riemann (Ruby) [1]. (Node streams have configurable backpressure/buffering [2].) Complex interconnected events can cause a runaway snowball effect if not carefully constructed or bound by limits: * Elm's "time-travel" debugger is so valuable because it allows introspection through an event chain that may not be linear. * Node takes a common approach, which is to push data/events through the stream but handle errors by bubbling up the stream processing chain. This Node approach maintains a hierarchy that is relatively easy to reason about. * React is popular because it effectively is FRP applied to the data model: the JSX view is the function, and the change in data model is the event. Since data model changes are limited, atomic, and one-way this makes React easier to reason about than other frameworks (Angular, I'm looking at you). This concept pre-dates React, I've used it since years ago with SpineJS and Knockout. Last but not least, when using streams there is an important tradeoff between speed/latency and delivery/processing guarantees, which is enough for its own discussion... [0]: https://github.com/nextorigin/godot2 https://github.com/nextorigin/godot2 [1]: http://riemann.io/concepts.html http://riemann.io/concepts.html [2]: https://nodejs.org/en/docs/guides/backpressuring-in-streams/ https://nodejs.org/en/docs/guides/backpressuring-in-streams/