News for hackers. Stuff that matters.
Re:Chrome's Most Important Feature by alttag on Wednesday August 31, 2011 @10:12AM (#2945579)
Because Firefox is very plugin driven, and its current design disables plugins that aren't compatible.

It is not in the best interest of users to have their plugins disabled automatically as a "feature".

Re:Chrome's Most Important Feature by thatjoshguy on Wednesday August 31, 2011 @11:28AM (#2945951)
Can't they just stop making changes that cause plugins and extensions to break?

I know that would be easier said than done, but Chrome seems to do a good job of it.

Re:Chrome's Most Important Feature by starwed on Wednesday August 31, 2011 @12:18PM (#2946212)
Firefox addons are traditionally written using the same API the browser itself uses. That's what makes them much more powerful than Chrome extensions, but clearly more fragile to breakage.

They're starting to offer a separate extension SDK (formerly called Jetpack) that allows extensions to ignore the internal API and build against something more stable. Such add-ons can be installed without requiring a restart, and should be much easier to update, but many important extensions need more power than currently provided. (Ad block is a good example.)

Re:Chrome's Most Important Feature by SkyMarshal on Wednesday August 31, 2011 @01:16PM (#2946493)
As is vimperator and pentadactyl.
Re:Chrome's Most Important Feature by mcpherrinm on Wednesday August 31, 2011 @12:50PM (#2946367)
In short: Not with the old API. In this recent newsgroup post, you can see a list of the things that could break an extension, and it's a lot.

http://groups.google.com/group/mozilla.dev.planning/browse_t...

The work to solve that is mentioned in the thread.

Re:Chrome's Most Important Feature by jerf on Wednesday August 31, 2011 @11:48AM (#2946060)
AFAIK, Chrome plugins still have much less access and power than Firefox plugins, which makes it easier for Chrome.
Re:Chrome's Most Important Feature by kalid on Wednesday August 31, 2011 @02:19PM (#2946821)
This is the tail wagging the dog. The plugins are going to be broken whether the update from 3 to 4 happens manually or automatically (and, if anything, discourages manual updating despite all the popups).

Windows has had binary compatibility for decades. Why not just version the internal browser API? (Extension XYZ was built against FireFox 3.6).

Re:Chrome's Most Important Feature by eurleif on Thursday September 01, 2011 @04:00AM (#2949065)
>Windows has had binary compatibility for decades.

Extensions don't just run on top of Firefox, though; they modify Firefox's UI in arbitrary ways.

>Why not just version the internal browser API?

Firefox already does this, and automatically disables incompatible extensions.