OSNews

If this proves true, then it would be interesting to see if this adds any weight to the calls for Microsoft to further release information on undocumented calls.
It could prove that Microsoft are deliberately hiding their best code their their own products (for want a crude description) thus hindering 3rd party programmers to better intergrate their applications with Windows (which is one of the many reasons MS have been taken to court over the years).

However, the realist in me expects little to come from any potential court case. Both sides are far too smart and have far too good lawyers to let anything significant harm (or good for their business opponents) happen.

That is just silly. It comes down to that a supported API has to be supported. If you want to use an unsupported API that is fine, nobody is stopping you, but don't complain to anyone when it is broken in the next point release. Sun does it in java, Apple does it in OSX, Linux doesn't really do it, but the linux devs dont maintain backwards compatibility, so the point is moot.

Secondly, something like DEP is something that should be managed by the system 99% of the time. The capability exists in post XP SP1 systems to manually muck with it in those 1% of corner cases. Public facing apps that execute arbitrary code off the internet are in those cases, so they wanted to use it. Since this ability was only really exposed to the world post XP SP1 (which was primarily about fleshing out security), they had to rely on a hacky way to do it.

This is not proof that MS is "hiding its best code", it is chrome trying to utilize an obscure feature of the APIs in operating systems that came out before it was publicly supported. I would say more then anything it is a testament to their thoroughness, since most people would have just said "we dont support pre xp sp1.", as it was a major upgrade that any xp user should have.