3 ms·
I'd like to give Rx a try (javascript mainly but .Net too) but it seems like a very large API to learn, and there seemed to be a lack of good resources last tim
by boothead 14y ago
I'd like to give Rx a try (javascript mainly but .Net too) but it seems like a very large API to learn, and there seemed to be a lack of good resources last time I looked.
Can anyone who's used it comment on their experiences or point me to some useful resources?
- justinweiss 14y agoI found this book to be pretty good: http://www.introtorx.com http://www.introtorx.com I'm not a .NET developer, but Rx was still one of the more interesting things I learned this year.
- boothead 14y agoSweet, thanks! I haven't seen that one before :-)
- xpaulbettsx 14y agoCheck out http://vimeo.com/43659034 http://vimeo.com/43659034, I gave a 1hr talk on this topic that is (imho) the best introduction to the topic
- skrebbel 14y agoif you're already familiar with LINQ, i feel that the step isn't so big. With Rx you're doing with a collection (more like a continuous stream) what you do with a collection of data items with plain LINQ. There's a few things more to it; notably the difference between hot and cold observables (but that's pretty well documented on MSDN). So I'd start learning plain LINQ (at least the main methods, such as Select, Where, Aggregate, SelectMany, Take) and using it more in your code. Notice how closely they map to many functions in libraries such as Underscore.js. Then, once you got that, imagine what you could do if you apply the same methods to repeatedly-occuring events. That's Rx.