Question

It is notice that more the addon slower the browser. it would be great if we could unable specific addon when it is requited. like for starting you do not need all the addons to be enabled.Search addon will work only when you go to search site & so on...

Answer 1

I think most of these concerns will actually be addressed with the Jetpack Add-on architecture - Jetpacks are significantly more compact and will load libraries only when needed, etc. :)

Answer 2

Yes but will all addons be ported to Jetpack? I don't think so. And will all addons be portable to Jetpack? Where is the future of addons? In Jetpack? Or keeping the original architecture. Even if Jetpack proves to be superior and is widely adopted, there will still be a long transition time to when every addon will be Jetpacked.

Then there is the question of how? I am not really au courant of the current architecture, and loading addons only wen required? Hmm. maybe if it is fast, but I don't want to even have to wait 1 second to use Firebug.

So the solution might be along the lines of loading all the core code for addons at startup, but leaving the addon to load its resources when there is need. Or something as a 'parallel' loading for addons: at startup, load the browser first, display it, then start loading the addons over time. Maybe make a 'prefered addon' order list, so most used addons are loaded first.

Actually, I remember when I tried developing an extension, to test it I had to reload the chrome each time a change was made. Removing or limiting that need would therefore make enabling addons without chrome reload possible, would it not?

It is an issue, especially with the Google Chrome browser appearing and having a startup time < 1 second overall. Even with NO addon, Firefox is slower.

Do we really have to wait for Jetpack?