Rx reactive framework

Been playing around with it a little now and i must say.. the author of this blog is not making an understatement, rx is the hottest thing since linq(-to-objects)

Having to use strings to make events into Observables is not optimal but thats the way of the compiler at this point it would be really great if they're able to change that in time for .net4 but rx is great in either case.

I did notice one thing though, Rx and tpl overlap slightly. both have mechanisms for joining things that happens at diffrent times. it would be interesting to hear the thoughs the two teams have about this and how the two techniques can be used together. it also seems synchroniation could be an issue with some of the Rx types. i wonder if they are using tasks and tpl constructs internally

At its core i dont think Rx isnt really responsible for dealing with threading and synchronization and that this is the responsibility of the various implementations. just like IEnumerable is not in it self thread safe but there are things like the tpl collections that are indeed thread safe.

Im bursting to find out more about Rx and the stuff thats around the two interfaces the fact that rx will be part of .net4 core framework is awsome news indeed

dude.. kid me not thats awsome!

but dont devalue your questions man, they're great

Have you already shot the interview by the way? (seems likely) if not, it'd be interesting to hear if Rx has made it into other places in the framework or if there are any plans on doing that. To hear those guys talk threading and sync would also be awsome

Im actually planning to use Rx in a little project of mine linked to project natal (using a hypothetical api unfortunatly)

its a very good fit because natal, like any input device is like a hose of updates that im looking to use as input to make updates of my own. rx would significaly ease the writing of that code and also use fewer threads/tasks that are just waiting for something to happen.

Rx will also help the system be more provider agnostic, the input updates are just an observable of some type, it doesnt have to be a natal, it could be test code or webcams or whatever.

for now i guess i have to write the thing as a silverlight library since thats the only way to get at the Rx bits at the moment but hopefully .net4 beta2 is not to far away (and hopefully Rx is in beta2 )

btw, i noticed that you canactually reference a silverlight assembly from a regular .net project (its the other way around that doesnt work) So this version of Rx can be used from any .net project and can also be used in vs2010 beta1

any news on that video? week is almost over

another Rx blog post, fresh of the twitterverse (confirming that Rx is going into .net4)

http://themechanicalbride.blogspot.com/2009/07/developing-with-rx-part-1-extension.html

dont forget part 2