Comments

This is a serious step backwards.  It looks like these guys don't realize classic ASP was a bad idea and we've moved on for good reason.  Don't know that inline SQL is a travesty, and isn't simpler, it's harder.

Instead of integrating out-of-the-box with good practices, OR/M (NHibernate), seperation of concerns, they have created a tweaked view language and encouraged terrible development.

Microsoft shouldn't spend it's time creating a bad toy, yet "another way" to do the same thing.  It should lead and encourage best practices, and make them as developer friendly as possible.

Kin was just another in a long line of failures by Microsoft in the critical mobile space.

http://www.engadget.com/2010/07/02/life-and-death-of-microsoft-kin-the-inside-story/

Windows Phone 7 is a hail mary pass, Microsoft will need a miracle or they will be out of the mobile business by 2011.  Ballmer should have been forced out as CEO when he handed the market over without even a fight.

Microsoft is correct to fix the developer experience on the phone, the competition has that truly wrong.  But developer experience alone cannot combat a huge market share and loyalty advantage.

While we do appreciate the explanation of SQL Azure pricing not considering CPU time vs. Amazon RDS, it still remains embarrassing that SQL Azure if toy-sized only.  Amazon RDS allows a terabyte database, Microsoft can only muster a puny 50GB?

If Microsoft was in any way serious about Azure they wouldn't insist on toy use only.

Extremely remedial.   Only for people who have no idea what automated testing is.

The Blue Box home screen is tragic.  Dead on arrival.  Have no idea why anyone would ever demo it except to make Steve Jobs laugh.

Nice to see MS work on IE after all these years, but why not demo Flash?  Silverlight?  If it  ships without both of those, it's road kill and Android takes #2 spot while MS is finished.

This is clearly the social media phone.  But, is it Facebook only, or is it able to adapt as the world changes?

All in all, this demo didn't recognize the competition.  Microsoft has stood by and let Apple score 3 unanswered touchdown passes.  The score is 21-0 and we're in the fourth quarter.   If it isn't far better than this demo, it looks like they are thinking about scoring one field goal. Ballmer should resign over the losses in the mobile space thus far alone.

Let's hope this demo does not show us WM7, or we all need to sharpen our Android dev skills.

Very nice.  Thank you.

I'd much prefer to see a correct model of Blackjack though.  Aces are worth either 1 or 11, and seeing such a flaw in an example is hard to take.   Hopefully, you'll show us how to actually do it in the next part!

Thanks!

This is just plain insulting.

If you care about F#, just see the Sample project that comes with VS 2010 and don't waste your time on useless crap like this.

This series was an amazing Christmas present for us all.   Erik's spirit of giving cannot be denied or underestimated.

Thanks!

Absolutely fantastic.  Up till now I though of comprehensions as conveniences, now I see they can be very elegant processing mechanisms.

I do wonder, if I tried to write this program using C# and as much Linq as possible, how far could I get?

Perfection.