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.
Thread beginning with comment 366778
To read all comments associated with this story, please click here.
Sounding familiar
by boudewijn on Wed 3rd Jun 2009 12:21 UTC
boudewijn
Member since:
2006-03-05

Those poor Chrome developers who need to work on Linux sound a lot like poor me when I have to develop on Windows...

(And for my dayjob, I work on an open source application that gets packaged as a binary installer for Linux, Windows and as an app bundle for OSX, so I know the hurt of all three platforms firsthand.)

RE: Sounding familiar
by bnolsen on Wed 3rd Jun 2009 12:27 in reply to "Sounding familiar"
bnolsen Member since:
2006-01-06

I'd have to agree.

Things taken for granted on Linux seem impossibly stupid on windows. Usually its a matter of grumbling, sometimes a group grumbling, then a half day to a few days of implementing a (grumble) workaround and making sure it works.

News must be getting lean nowadays.

Reply Parent Bookmark Score: 5