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...
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.