Comment on This is why memory fragmentation is badparentComments−william4215yThat'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−lmz15y> 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 bootAre there really that many Firefox extensions that use native code?−udoprog15ySide 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.−mnutt15yWhile most Firefox extensions are in JS, I believe you can bind to native c++ as well.−lmz15yChrome also allows you to access native code in extensions using NPAPI plugins: http://code.google.com/chrome/extensions/npapi.html
Comments
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
> 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?
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.
While most Firefox extensions are in JS, I believe you can bind to native c++ as well.
Chrome also allows you to access native code in extensions using NPAPI plugins: http://code.google.com/chrome/extensions/npapi.html