Linked by Thom Holwerda on Wed 3rd Jun 2009 11:21 UTC, submitted by Hakime
Google One of the defining features of Google's Chrome web browse is its sandboxing feature. You probably won't realise it's there, but from a security point of view, sand-boxing is one of the most impotant factors in browser security, as it severely limits the amount of damage a security hole can do: sure, you've got a hole in the browser, but thanks to sandboxing, you're pretty much locked in - until you break out of the sandbox, of course. Sandboxing on the Windows variant of Chrome was a "complicated affair", says Chromium developer Jeremy Moskovich, but for the Mac version, it's all a bit easier and more straightforward. On Linux, however, it's a mess.
Permalink for comment 366799
To read all comments associated with this story, please click here.
do it one distro at a time
by aeischeid on Wed 3rd Jun 2009 14:37 UTC
Member since:

Maybe application developers should not worry about developing for 'Linux' as that is sort of impossible due to its nature. Maybe they should just go one distro at a time. developing Chrome for Ubuntu, Fedora or OpenSuse would be doable I would think. Google could pick their favorite distro or the easiest distro for them to develop on. This just seems like the most common sense way to go about it to me.

Edited 2009-06-03 14:38 UTC

Reply Score: 1