On thing I thought revealing was the author�s blaming Microsoft for being �tied down� to a crummy OS structure because they have to support old versions, and then slamming them for coming up with a new version that doesn�t support older version of software.

Well, that's not his fault that it happens. And by "not support" I believe he means two things: (1) the older s/w won't run, and (2) the newer s/w won't always work with data files from the older s/w -- a problem I frequently run into when helping unfortunate friends with upgrades.

soon you won�t be able to run anything on Windows but Microsoft products, an idea I find preposterous.

That's definitely the goal. Initially, it will just mean you cannot build apps that run without a big WARNING pop-up, unless you fork over $$$ for a certificate or something --> kinda like trying to do independent SSL on a website today (who'd have thought..). This is intended to shut out Open Source.

The next phase will be not being about to build apps at all without coughing up blood for a certificate. This is intended to grab revenue and completely shut out Open Source for good.

And finally, they just stop issuing certificates outside of MS, or just raise the certificate price to the stratosphere (nearly the same effect).

No doubt whatsoever.