The generalized "is" statement at 31:19 is just like the ability to declare a variable in any statement that didn't seem to make it into C# 6. Why not just finish that feature and add this as a new use case for it?
Touching at 49:43 on the commentary about how Swift is "harsh" about how it treats null. The biggest "harsh" parallel in C# for me is the ban on unsafe iterator and async methods. It is arbitrary and I have to write tons of boilerplate to get around it, which is what I'm using C# to avoid in the first place! If I'm daring enough to declare pointers, that should settle it.
Does this work successfully across separate UI threads inside the same process? That was always the one key use case that every other desktop framework barfed on and it made scaling large apps a very annoying process.
It seems like the real problem is that the Windows world doesn't treat the Administrator account as rare and sacred as the Unix world treats the root account. You generally can't load an arbitrary driver with CreateService() unless you're an Administrator, yet a fresh desktop install always starts me right off with Administrator privileges. This does not compute!
I still don't know what exactly the Java world thinks it has on C#/.NET... this is very quickly becoming Direct3D vs OpenGL where Microsoft entertained the illusion of an even match for a little bit in the beginning...
Does anyone actually write WinRT apps or does everyone just write WinRT demos? Why are we doubling down on reinventing the wheel here at a snail's pace, agitating WPF and Silverlight developers until they leave for other platforms? When you lost Josh Smith, that should have been a dire wake-up call. I don't think anyone had as much passion for XAML and WPF, and you screwed him with this abomination called WinRT. Now his income comes from teaching .NET developers how to migrate to Apple platforms.