Paul Thurrott: “Microsoft has an unfortunately inaccurate high-level diagram showing the relation between WinRT and the environments its replacing (which are shown as IE, Win32, and .NET). But the important thing to note is that there’s the NT kernel and then, right on top of it (like Win32) is WinRT. This WinRT has an application model and three boxes of capabilities that are expressed by APIs (Communications & Data, Graphics & Media, and Devices & Printing). “Above” WinRT is the two sets of presentation layer/programming language couples: XAML and various high level programming languages (C#, VB, and so on) and HTML/CSS and JavaScript, respectively. (DirectX is left out, but this sits on top of WinRT too.)”
In an earlier post, Windows 8 Speculation, I had diagrammed some options for WinRT. It looks like Microsoft went with the middle choice, making WinRT a peer to Win32. This is a very good thing.
Now I’m pretty excited to see what the API’s look like.

A pretty fair review from a man that develops for Mac and iOS. As a developer it’s interesting to see how Justin feels about Visual Studio. It’s how I feel about Xcode. Xcode is super nice, but I just can’t get used to Interface Builder. He also had some words to share about his attempt at Android development, not stellar, but I wouldn’t expect that from someone that’s used to using great tools to do their job. Both Microsoft and Apple provide superior development tools. Android is going to be a bit more work, more hackerish. 
