Bart De Smet explains the design philosophy behind the reactive framework Rx, the combinators and operators defined by Rx, and the work in progress to integrate it with async.
Bart De Smet is a Software Development Engineer on the Cloud Programmability team, an avid blogger and a popular speaker on various international conferences. In his current role, he’s actively involved in the design and implementation of Reactive Extensions for .NET (Rx) and on an extended “LINQ to Anything” mission. Before joining Microsoft, Bart was a C# MVP for four years.
QCon is a conference that is organized by the community, for the community.The result is a high quality conference experience where a tremendous amount of attention and investment has gone into having the best content on the most important topics presented by the leaders in our community.QCon is designed with the technical depth and enterprise focus of interest to technical team leads, architects, and project managers.
Trottle events and being able to write unit test for race condition?
Rx isn't only less management for setting up and disposing publish/subscribe at halfway the talk trottling your event stream is explained. That't just amazing.
At the end he even mentions (but not explains because of lack of time) that with Rx you can write unit test for race conditions because Rx has schedular for that.
At first I thought that Rx competed with Task parallel and P Link. It's focus on asynchonusity could make your app perform beter on a multicore cpu, but it's more about making your app more responsive. This makes it much more fundamental, because the user experiance is always important and performance is only intresting if it's lacking.