Exactly. Rx was created by MS research for Azure -- mostly to abstract away the threading model in the cloud - why reinvent the wheel when Observable &#x2F; Rx is built for every platform you use and is fantastic.<p>When ELM came along with its signals, im like, meh, why not Rx? Im not even going to bother to learn it, your at v0.1 and ur gonna see why u need it soon enough. Subcritiption? Dont reinvent the wheel like Redux? Why not Rx? A few months later, everyone is going &quot;how we we handle async actions properly?&quot; Well thats an Observable my dear friend!<p>Just like when Flux &quot;came out&quot;. They just rebranded Event Sourcing in the client UI.<p>Im getting pretty fed up with all this mumbo jumbo. I write C# mostly, i like FRP, ES, unidirectional flows. Im going to bring a slim universal c# solution with a typescript&#x2F;JS bridge to the OSS community. The main philosphy is, one client&#x2F;server architecture, to build scable responsive apps. With builtin backpressure handling.<p>If ppl had just embraced Rx like 6years ago when it was first V1&#x27;d, imagine how much further along the road we would be now? Like seriously, get over urself OSS fanboys, just cause its MS, doesnt mean its bad.