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.

Each time I read about Chrome developers saying bad things about development on Linux, I just laugh. That wiki page says root installation is not good option, what a joke

Do Chrome developers, expects to do the same crap they do on Windows, to install a binary on %LOCAL_APP_DATA% for each user????? do they understand the name says DATA!!!!! not programs, what they will do next time MS enforce better security policies and do not allow executable on Data directories, scream monopoly and that they are attacking Google, follow the good practices for the platform you are developing, for Linux, create a deb and an rpm and create a apt/yum repo like Adobe do for flash, use the system updater instead of the internal one on chrome