Reminds me of when Microsoft's marketing-based product management crazily shoehorned the ".Net" moniker onto everything that the company sold whether it made sense or not. Now the actual .Net technology was pretty nice when everything settled down - but I don't understand now that Microsoft finally managed to make decent virtual machine technology foundation, why they're pushing forward with a path with Windows 8 (ARM) incompatible with Win 8 (x08) why not something a bit closer to run everywhere on a VM?
I'm assuming you can do that and MS will encourage people to write code for .Net rather than C++. You would probably need to add some thing for metro but I'm guessing MS will try and make it as painless as they can.
If this is confusing people on HN, think what it will be like for consumers since the two devices look very similar. Imagine trying to explain to someone that their laptop can't run software X that someone else's otherwise identical (or near enough) laptop can because "it has an ARM chip not an intel one".
Instead of saying " Supports Windows 8 " , non metro software will now have to say " Supports Windows8* "
I wonder how many developers will bother with metro since we already have a bewilderingly huge choices of platforms to support with our software, including "Just give up and do a web app".