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."
Thread beginning with comment 331190
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[4]: Let the OS wars Begin!
by sbergman27 on Tue 23rd Sep 2008 21:05
in reply to "RE[3]: Let the OS wars Begin!"
Member since:2005-07-24
they would never break sandbox of Chrome from the kernel side (except unintentionally, but when that happens, it is fixed as soon as it's discovered).
And usually results in an entertainingly colorful quote, not always suitable for mixed company, from Linus himself, to grace the kernel page of LWN's Weekly Edition. ;-)
RE[4]: Let the OS wars Begin!
by kaiwai on Wed 24th Sep 2008 04:28
in reply to "RE[3]: Let the OS wars Begin!"
Member since:2005-07-06
Then obviously you've missed the NGPL vs. NTPL vs. Old Threading, where application compatible was not assured when Linux moved from the old threading model to the (which is used now) NPTL. I remember wine breaking because it relied on features based on the old fork() process idea of creating 'fake threads'.
Recent Original Stories
Recent Comments
Headlines
Random Comments
Random Stories
Random OS Link
Member since:
2006-01-17
Linux devs DO mantain backwards compatibility, and it would precisely apply in this case - they would never break sandbox of Chrome from the kernel side (except unintentionally, but when that happens, it is fixed as soon as it's discovered).