Subscribing a subject to a cold observable broadcasts its notifications to multiple observers, thus making it hot. Woah, so this is what multi casting is about! So it’s clear there are only two scenarios where it’s correct to use subjects: - The source is external and cold, and I want a hot observable. - The source is local and I want a hot observable. use either `Defer` or `Publish` to change the temperature accordingly That’s where `Publish` is useful, as described earlier in this post. `Publish` converts a cold observable into a hot observable; however, it returns `IConnectableObservable`, which requires a call to `Connect`.

Elm is about making delightful projects. [...] Projects you are excited to share. Projects that get you excited about programming! That means I am always asking myself how Elm can be simpler. How can it be easier to learn? More fun? Quicker for prototyping? More reliable? I think my obsession with these questions are the heart of Elm's design philosophy and Elm's success.

Introduction Operator-fusion, one of the cutting-edge research topics in the reactive programming world, is the aim to have two of more su...

Within hours of yesterday's post, I had some new information to consider.

The full panel Q&A and discussion with Josh Abernathy, Justin Spahr-Summers, Uri Baghin, Dave Lee, and Jon Sterling from the 2014 Reactive Cocoa Developer Conference hosted by GitHub. As always, feel free to leave us a comment below and don't forget to subscribe: http://bit.ly/subgithub Thanks! Connect with us. Facebook: http://fb.com/github Twitter: http://twitter.com/github Google+: http://google.com/+github LinkedIn: http://linkedin.com/company/github About GitHub GitHub is the best place to share code with friends, co-workers, classmates, and complete strangers. Millions of people use GitHub to build amazing things together. For more info, go to http://github.com

Let's start discussing Apple's Combine framework by discussing what's missing

Apple has released their take on RxSwift. In order to understand it, one must start from the beginning.

Get started with Apple’s Combine with your existing RxSwift knowledge

GitHub desktop developer Justin Spahr-Summers presents a case for what the future of ReactiveCocoa might look like at the 2014 Reactive Cocoa Developer Conference hosted by GitHub. As always, feel free to leave us a comment below and don't forget to subscribe: http://bit.ly/subgithub Thanks! Connect with us. Facebook: http://fb.com/github Twitter: http://twitter.com/github Google+: http://google.com/+github LinkedIn: http://linkedin.com/company/github About GitHub GitHub is the best place to share code with friends, co-workers, classmates, and complete strangers. Millions of people use GitHub to build amazing things together. For more info, go to http://github.com

Cross posted from http://channel9.msdn.com/Shows/Going+Deep/Expert-to-Expert-Brian-Beckman-and-Erik-Meijer-Inside-the-NET-Reactive-Framework-Rx Erik Meijer and team (developer Wes Dyer, in particular) have created a profound and beautiful .NET library that will take managed event based programming to new levels. Of course, many of you wish that you could write LINQ expressions over events. Well, now you can thanks to Erik's and Wes Dyer's latest creation, Rx - .NET Reactive Framework. Erik, being a fundamentalist functional theoritician, can't create new programming abstractions without employing some form of monadic magic. Enter astrophysicist and monadic composition wizard Brian Beckman. The last time Brian was on C9 he taught us about the State Monad. At the end of that discussion he mentioned he wanted to teach us about the Continuation Monad next. So, who better to conduct this episode of Expert to Expert than Dr. Beckman? Yep. You guessed it! Rx employs the Continuation Monad in its composition. Erik is in the hot seat this time and it's always a real pleasure to converse with Erik and Brian in the same room at the same whiteboard. Now, what is Rx? The .NET Reactive Framework (Rx) is the mathematical dual of LINQ to Objects. It consists of a pair of interfaces IObserver/IObservable that represent push-based, or observable, collections, plus a library of extension methods that implement the LINQ Standard Query Operators and other useful stream transformation functions. Observable collections capture the essence of the well-known subject/observer design pattern, and are tremendously useful for dealing with event-based and asynchronous programming, i.e. AJAX-style applications. For example, here is the prototypical Dictionary Suggest written using LINQ query comprehensions over observable collections: Please subscribe to this Channel 9 interview to be notified when we have clearance to distribute Rx over the counter (lame puns intended Smiley. Tune in. This should prove to be an instant classic besides being a very important episode of E2E. Rx is deep, man. Deep. Enjoy!

Recommendations for effective view models when working with RxSwift.

The backing GH issue thread is wonderful https://github.com/ReactiveCocoa/ReactiveCocoa/issues/2190

It’s a collection of small functions and properties without a linear story. ​ Part of me does not want to encourage people to use RxSwift for the reasons I’ve outlined. But part of me very much wants to encourage people to use RxSwift — because change comes, in part, from the community pushing the state of the art. ​ But if you do use it, and some time in the future there’s a nice, declarative way of handling events and dealing with state, then I’ll have you to thank for helping make that come true.

At Grailed we’ve turned to functional programming for inspiration on how to write testable, well-structured view models.

“Free map functions express the nesting nicely: map: ((A) -> B) -> (Signal) -> Signal map: ((A) -> B) -> ([A]) -> [B] Then the nested map is function composition: (map < map): ((A) -> B) -> (Signal

it’s likely that the iOS team can crib their solution, platform differences aside. That’s very powerful, as it leads to us all speaking a common language, even though our actual languages are very different.