5 Differences Between Firefox Add-ons And Chrome Extensions
Finally, Chrome has got extensions ‘officially’ and we have more ways to customize the browser. At very first instant, Chrome extensions feel exciting but the fact of the matter is that they are still in early development stages.
- You can create Chrome extensions easily. Though, with sound knowledge of HTML, JavaScript and CSS you can create add-ons for Firefox and Chrome both but Chrome APIs are easier to work. Once again, APIs are in earlier phase and a lot of features are yet to be implemented.
- Chrome does not have REAL extensions at the moment. Extension gallery lists over 500 extensions but none of them is really awesome – most of them are just ‘Chrome’ versions of popular Fx add-ons. I am missing features of Adblock plus (don’t tell me that it exists for Chrome!), NoScript, FireFTP, Greasemonkey (fully featured), RefControl etc.
- In Chrome, you don’t need to restart browser after installing, enabling or disabling extensions. That’s best thing about them.
- Chrome extensions get updated automatically – as the developer uploads the new version. In Firefox, a developer uploads a newer version – and the World waits for its approval (which may take even months!).
Though, Mozilla team has accelerated this process in the past month and it takes lesser time now. Well, thankfully Mozilla approves all extensions and their versions before they go public and this is safe for users. 
- Chrome will have built-in support for userscripts. (In Firefox, we need to install Greasemonkey (or Stylish) add-on.) Though, Chrome does not support GM APIs at the moment but the good news is that Aaron Boodman (creator of GM) now works with Chrome extension team (Source: RWW), so we can expect something big in future.
Also see: Check And Change Google Chrome Release Channel
Must Read These Posts:
tsuvik (Vikas SN) Said,
RT @arpitnext 5 Differences Between Firefox Add-ons And Chrome Extensions
Mony Said,
While every article I saw fully praising Google Chrome, you are the first person to come up with pros and cons in both sides. Regarding the approval process, Chrome is very young and a very less number of add ons are available for it so I think approval process will be easier for them. But for Firefox they need to examine a lot of add ons to approve so the approval process naturally takes more time than Chrome. This is my opinion. If I am wrong please correct me.