1 - http://msdn.microsoft.com/en-us/library/ie/jj193557(v=vs.85)...
It's true that it runs on desktops. But it's also true that it's primarily intended as the version of the browser that's used on touchscreen devices.
The whole kerfuffle here centers around the ambiguity of the terms in use. It is unfair to take the blog author to task over his language, only to use unclear language in return. Characterizing this as the "mobile version" of the browser is incredibly unclear, considering it's the default on the OS that will ship with desktop and laptop computers.
EDIT: Here's a little matrix I posted further down the page. I think this makes the context a little more clear.
Windows UI | Desktop
(default)
================================+================
Tablet or phone : Affected | N/A
Desktop or laptop: Affected | NOT affectedAs far as the whole "mobile/not mobile" thing goes, I think that ambiguity is totally inescapable on Windows 8. Windows 8 has an identity complex, and is full of bits of UI that were clearly designed for touchscreen devices but are also used on the desktop OS. But I don't think the fact that they're available negates the fact that they're primarily optimized for a mobile experience. It's more just a symptom of Microsoft trying (and, as illustrated by cases like this, not necessarily succeeding) to shoehorn a mobile experience and a desktop experience into the same environment.
You have to wonder how many people will never switch modes...
Its kind of crazy to me Google doesnt include Flash with jellybean when it works just fine. I'm all for killing flash asap, I hate it... but when it works... why deprive people of that bullet point feature?
Either way, its beyond false to call Android (even jellybean) a "flash free platform". You have to download and install flash on a desktop computer, just like you have to download and install Flash on Jellybean. Still works like a dream though.
The whitelisting only applies to the "mobile" version of their browser. To that end, Microsoft's policy is markedly more Flash-friendly than what's happening on other Mobile platforms. After all, at least some Flash content will be permitted. By contrast, iOS and (as of recently) Android are effectively Flash-free platforms.
I think the fact that there's no restriction on desktop, combined with their published requirements for how to get whitelisted for mobile, make it pretty clear that this isn't really meant to be an attack on Flash. It's more an attempt to deal with the large number of websites whose Flash content is fundamentally incompatible with touchscreens because it assumes the presence of a mouse. Blocking Flash on those sites hopefully results in a better user experience because the site is theoretically degrading to a Flash-free version instead.
Far from being a Flash-killing move, in hindsight the other mobile platforms adopting a similar policy might have been the one thing that could have saved Flash for them.