News for hackers. Stuff that matters.
Re:This is why memory fragmentation is bad by william42 on Tuesday July 05, 2011 @06:43AM (#2729350)
That's because 1) Chrome is better-designed 2) Chrome extensions are JS and not native code, meaning they're less likely to leak due to programmer error, and there are fewer of them, to boot
Re:This is why memory fragmentation is bad by lmz on Tuesday July 05, 2011 @08:34AM (#2729562)
> 2) Chrome extensions are JS and not native code, meaning they're less likely to leak due to programmer error, and there are fewer of them, to boot

Are there really that many Firefox extensions that use native code?

Re:This is why memory fragmentation is bad by udoprog on Tuesday July 05, 2011 @09:42AM (#2729755)
Side note: Firefox extensions aren't native code, they're written in JS.

EDIT: I do however agree that chrome is more well designed. Firefox has been through a lot of iterations through the years.

Re:This is why memory fragmentation is bad by mnutt on Tuesday July 05, 2011 @11:17AM (#2730131)
While most Firefox extensions are in JS, I believe you can bind to native c++ as well.
Re:This is why memory fragmentation is bad by lmz on Tuesday July 05, 2011 @11:51AM (#2730296)
Chrome also allows you to access native code in extensions using NPAPI plugins: http://code.google.com/chrome/extensions/npapi.html