Linked by Thom Holwerda on Tue 23rd Sep 2008 15:38 UTC
"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."
Permalink for comment 331207
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
Recent Original Stories
Recent Comments
Headlines
Random Comments
Random Stories
Random OS Link
Member since:
2005-07-24
You are confusing the internal API (which is used by drivers and other kernel code) with the user space API. Research the matter and you will see that I am right. In fact, it is because so many people hold the same misconception that I took care to clarify the matter. Otherwise I would not have bothered.
If you still disagree, please point out a specific example for us to examine.
Edited 2008-09-23 23:13 UTC