Comments

Concurrent<T> looks very similar to the EventLoopScheduler in the Reactive Extension library (Rx). Nice feature to have the Thread.Join in the destruction. Also nice to get the result back in a future, however .NET would just use Tasks<T> for this. Scheduling is a slightly different problem space, better suited for the fire and forget problem like the logging example.

Good session as usual

Lee

.NET dev,  but interested in what ever Herb says

IE was the best browser from v4.5 to v6 (or 1998 to 2004/5)
Paul is spot on, IE6-9 was a really poor experience compared to Google's Chrome and FF.
M$ marketing budget maybe wasted here. First make sure IE actually doesn't suck any more (maybe it doesn't but my fingers have been burnt), next gain a natural following by having a product that doesn't suck.
The only people marketing will work on are the people who cant make the critical analysis for themselves, these are the people that will have just used IE all along because it comes with windows.
The only way to get a loyal following back, is from a quality product....and time (for those old wounds to heal)
I want IE to be good (like .NET, Win8, SQL Server, WP, XBox). Installing Chrome is a pain in the rear, just less of a pain than using IE.

@Minh You can also get the zero-to-hero guidance from www.IntroToRx.com. If it doesn't provide what you need then (as you sound like the target audience) then we will try harder for version 2 of the book/site, if you provide the feedback.

These quick videos are perfect. Keep them coming. 

Sorry to hear you dont like Win8/Metro as much some others. The swing for me was when some one (I think in a c9 video) said, 'Oh yeah, Metro is just the Start menu but more powerful'. *penny drop*!

You totally can kick back to desktop (which is where I spend most of my time). All the old tricks are still there, my fav being WinKey+"anything" to search for "anything".

I am loving Win8 and think the guys at MS have done a great job.

@Maddus, I think there is still a cost of making all events (just a multicast delegate) into subjects (classes with state and behaviour). In your own project you can easily favor IObservable instead of events, and I agree that 90% of the time, they are much better.

@Maddus, @Felix, @Alex, I too thought there was a little bit of content lacking on Rx. The Videos are awesome, but searching blog posts, video etc can be hard work. So, I bit the bullet and wrote the book on it. It is free, check it out @ www.IntroToRx.com. I am still waiting on the eBook generators to give us a good output before we can publish to Kindle etc., but all the content is right there on the site. -@Charles, feel free to plug the book dude, share the love

[23:56] VMRole doesn't have persistent disk, where as VMRole does.

I think this is meant to be VMRole doesn't have persistent disk, where as VM does.

Is that right?

Nice overview Mike. I thought a nod to Rx was an obvious omission. Rx would save you writing the boilerplate code for your Observable classes.

Would love to see more.

Lee

Booting too fast? Sounds like a "Champagne Problem", our favorite kind of problems.

Cheers. As a C# dev this helped me understand the syntax (:: << etc) more than anything. Most of the rules seem quite similar to the C# rules which is nice.

Good work.