[wisty]

Still, there's no reason to break bugfixes. Heck, a lot of them still work, if you flag some "developer mode", but you don't need to do that in Chrome.

Who care's if Mozilla has more extensions? They cause too much trouble when you upgrade.

[jokermatt999]

Who care's if Mozilla has more extensions? They cause too much trouble when you upgrade.

I do. TreeStyleTab and Pentadactyl essentially change Firefox into a different browser that I much prefer. There's nothing like that on Chrome, and until they get better capabilities for extension writing, there won't be. The day when they have working full replacements (not Vimium and the mediocre sidetabs option), I'll happily switch to Chrome, but until then I'll take having my nice customized browser.

[colincsl]

"Who care's if Mozilla has more extensions? They cause too much trouble when you upgrade."

Exactly. I switched to Chrome because of this and Chrome's better (less buggy!) Sync features.

[ZoFreX]

I don't think it really counts as an "upgrade" if you opt-in to a beta.

[lurker19]

True, but unless FF adds a "re-version-tag my addons based on feedback from testers" feature, we will get bitten when FF5 final comes out and disables all existing deployed extensions.

[gmac]

In actual fact, they've changed the process so this generally won't happen:

http://blog.mozilla.com/addons/2011/04/19/add-on-compatibili...