Jafar Husain, and myself (Matthew Podwysocki) will also be giving the talk at QCon NYC in June: https://qconnewyork.com/presentation/end-end-reactive-progra... in addition to a great tutorial that we put together: https://qconnewyork.com/tutorial/functional-programming-js-w...
But, if you're interested in playing with it yourself, we have it listed here: http://reactive-extensions.github.io/learnrx/
They certainly have some interesting technology.
I would hope so based on the salaries they pay their engineers
If anyone has the time and inclination, I'd love some feedback.
Also, is ReactiveCocoa what most people would use to do this in ObjC? https://github.com/Reactive-Extensions/Rx.ObjC doesn't seem particularly active.
I've been using bacon.js in conjunction with Facebook's React to write more of my application declaratively. React automatically updates the DOM when bacon properties change.
As the primary author of RxJS, I'm curious why you chose bacon.js over RxJS.
Anyhow, these architectures go well together!
> I'm curious why you chose bacon.js over RxJS
At the time I made the decision, Bacon had documentation and RxJS didn't (at least, not that I could find). I was new to FRP, so that made my decision for me -- I never went back and reconsidered.
Are you aware of any advantages RxJS has over Bacon? It looks a bit more extensive in general, so now I wonder what I'm missing out on :)
Direct Link: https://www.youtube.com/watch?v=XRYN2xt11Ek
Streams are to promises what lists are to maybes (options).
Promises on the other hand, are more for scalar values and composition is rather limited based upon that. However, RxJS plays very well with Promises such as the following: https://gist.github.com/mattpodwysocki/b57cf50a34f22ba39e4f . This really shows where Promises leave off and true good composition starts.