again with the wrong abstractions

[Raoul Duke]

RxJS starts out with a lie that everything will fit cleanly easily into the Observable-Observer design with simple use of Observer.{next,error,complete}() ... but then all the "exceptions" show up and aren't statically detected and have all sorts of cargo cult patterns and workarounds (eg how people use BehaviorSubject). 

is there yet any actually good approach to streams that isn't a house of tissue of lies of resource leak footguns?

I am ever more of the opine that as terrible as React is, it makes so much more design sense than anything i've ever seen that is "Reactive". It bugs me that Reactive is such a hyped thing.

[Mike Austin]

The idea is nice, but needs to be part of the language. As a library on top of an imperative language... I don't know.