Comments

Great talk. Though I have to say this wrapper pattern has been pretty common in the C# world for a while (sans operator())

I'd say that putting the "save" button in the on-demand app bar is not appropriate here - Save is functionality that is required as part of the core function of the page (as is clear from the fact that when the page is not saved it tells you that it's not saved) so it should be visible on the page canvas.

http://msdn.microsoft.com/en-us/library/windows/apps/hh465302.aspx :

Don't put critical commands on the app bar.

Don't place commands that are core to what makes an app great on the app bar. For example, in a camera app, place the  "Take a picture" command on the app page rather than in an app bar. You could either add a button to the app page or simply let people tap the preview to take the picture.

@Charles: Awesome, looking forward to watching all those ... but what about "Going Deep: Inside WinRT XAML"? Or here's an idea, you could do an Expert to Expert with Erik Meijer and someone from the XAML team, and talk about the relation between Reactive Programming and data binding engines such as XAML's ... or you could even try to get Paul Betts on to talk about ReactiveUI ...

P.S. Now that you've created a nice anonymous structural typing feature here, please port it back to C#. It would come in handy for ViewModels, for example ...

This looks pretty sweet - addressing not only some of my JS gripes but some of my C# gripes as well (structural typing! woo!)

cool hack, but it kinda reminds me of this: http://www.youtube.com/watch?v=120R2-phK0U

The "shortcut" I think is most important to know for the charms is that you don't really have to "hover" in the corner and wait for them to appear before moving up/down to the one you want. It works much better if instead you "swoop around the corner" in one continuous motion. This is not only faster, but also feels nicer and is more reliable because the momentum from moving to the corner will continue and prevent you from falling out of the edge.

Very intrigued who the people they're working with are who are looking for C ...

Awesome.

I remember William Cook for an illuminating paper of his from 1990:

  "Object-Oriented Programming Versus Abstract Data Types"

http://www.cs.utexas.edu/~wcook/papers/OOPvsADT/CookOOPvsADT90.pdf

I really recommend reading this paper if you want to get a clearer picture of the relationship between object-oriented programming and functional programming of the Haskell/ML style. At least, it did that for me.