Linked by Thom Holwerda on Tue 23rd Sep 2008 15:38 UTC
Google "Since its release a few weeks ago, curious developers have been sniffing through the source code for Google's new Chrome web browser. Chrome's source is interesting for a variety of reasons: there's the new V8 JavaScript virtual machine with its boasts of near-native code performance, the WebKit rendering engine that does all the hard work of understanding and displaying web pages, and (last but not least), Chrome's secure sandbox designed to minimize the impact of any security flaws that might exist in both the browser and plugins alike. It is this secure sandbox that has piqued the curiosity of some observers, and for a reason that many may find surprising. From reading the source, it looks as though Google has reverse-engineered Windows, and that's explicitly prohibited by the Windows EULA."
Thread beginning with comment 331162
To view parent comment, click here.
To read all comments associated with this story, please click here.
Bill Shooter of Bul
Member since:

Well, yes, but its also very tempting for developers at Microsoft to use those undocumented OS api functions in their programs ( word, live antivirus, IE, Media player). And they often do, leading to an unfair advantage. They can't claim to be protecting the third party developer, if they themselves are using it in an application. BTW, apple also does this a lot.

Reply Parent Score: 6

ebasconp Member since:

IMHO, they're their APIs, they can do whatever they want with them... they do not have TO publish and document every function their APIs provide, and, though the Win32 APIs are always criticized, they have better documentation than a lot of other commercial APIs...

Edited 2008-09-23 19:00 UTC

Reply Parent Score: 1

Morgul Member since:

IMHO, they're their APIs, they can do whatever they want with them...

If we were talking about anything other then Win32 APIs, I'd agree with you. However, to think that we should be grateful for documentation this good... well, it's a tad naive.

We're talking about an API that 90% of all applications (or more?) need to use. Windows is The platform to develop for. When you're API is that critical to the software ecosystem, you had better document everything and it had better be documentation that makes Kernighan and Ritchie cry tears of solid gold.

Reply Parent Score: 2

PlatformAgnostic Member since:

If it doesn't ship in the Windows box, it can't use APIs that are not doc'ed in MSDN.

Reply Parent Score: 2