Loading user information from Channel 9

Something went wrong getting user information from Channel 9

Latest Achievement:

Loading user information from MSDN

Something went wrong getting user information from MSDN

Visual Studio Achievements

Latest Achievement:

Loading Visual Studio Achievements

Something went wrong getting the Visual Studio Achievements

Bart De Smet: Rx, LINQ, AMA

26 minutes, 5 seconds


Right click “Save as…”

The great Bart J.F. De Smet joins Charles Torre for a conversation about Rx, LINQ and whatever else comes up - questions come in from the Internet via Twitter. Thanks to those of you who submitted questions! That's why we do this Smiley

Follow the discussion

  • Oops, something didn't work.

    Getting subscription
    Subscribe to this conversation
  • Again, i'd just to clarify, the reason im on about Bcl is that i think it would greatly speed Rx adoption within the framework itself.. i'd like to see more apis expose iobservables especially in wpf/xaml.. rx support in databinding? yes please Smiley language support? one can dream..

    I think rx is a really fondational technology that almost every app can use. its the same (but opposite) as IEnumerable for crying out loud Smiley

    i ask you this, what could .net be like if only the IEnumerable interface was in the Bcl and all the combinators lived in a separate library?

    I really hope you dont think i'm trying to troll you or be a jerk, i just think rx is awsome and the bar of entry should be as low as it could possibly get

  • CharlesCharles Welcome Change

    @aL3891: Of course we don't think you're trolling, man! The key issue - in my opinion - is that once you embed Rx into the BCL then:

    a) Bart and company will lose agility (and most likely full control over its evolution...)

    b) Rx updates become locked into BCL's updates (so, versioning is slowed down, see a)

    c) Erik will lose even more hair  Smiley


Remove this comment

Remove this thread


Comments closed

Comments have been closed since this content was published more than 30 days ago, but if you'd like to continue the conversation, please create a new thread in our Forums, or Contact Us and let us know.