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."
Permalink for comment 331174
To read all comments associated with this story, please click here.
More to the point...
by Morgul on Tue 23rd Sep 2008 18:58 UTC
Member since:

...this will never see a court case. Microsoft and Google may be 'adversaries', but the point is Microsoft won't press Google on a EULA. You have to remember: Chrome is windows only at the moment. (I say this as my laptop is compiling the latest linux codebase) If anything I can see Microsoft volunteering more information to Google, to help "improve integration" with windows.

Think about this like someone who owns a business: Your competitor has spent a good deal of money and time promoting a new product. They've stirred up a veritable hornet's nest of opinions, but for now, their new product only runs on top of your product. An opportunity exist here. You can 'parter' unofficially with your competitor, work towards 'interoperability, meanwhile riding their coattails, and making sure that they're as locked into your product as possible.

If Microsoft is foolish enough to pursue anything along the lines of a lawsuit, I will be shocked and appauled.

Reply Score: 2