3 ms·
FireFox gets a lot of flack for it because of plugin support. We use GWT for an internal webapp and the developer plugin is not compatible every time they do a
by ismarc 14y ago
FireFox gets a lot of flack for it because of plugin support. We use GWT for an internal webapp and the developer plugin is not compatible every time they do a release of FireFox (it really is, but packaging makes it not). New machine? Grab off of a mailing list. Tired of daily prompts to upgrade? Hit cancel when it isn't listed as compatible. This happens often enough and is annoying enough that the GWT developer plugin is the only one I use now. Chrome, on the otherhand, really does have seamless upgrades.
I know FireFox has a more robust plugin architecture and half the time is the plugin developers' fault and FireFox has been working on a new plugin system for a while, but it's the same problems FireFox had with upgrades for years, they just happen more frequently, exacerbating the problems.
- drivebyacct2 14y agoI assume you mean "extension" everywhere you've written "plugin".
- ismarc 14y agoPotentially, I just remember from having fought with this late last week with the GWT Developer one, which was called the "GWT Developer Tools Plugin", and I can't ever remember what Firefox calls a Plugin vs. Extension vs. Add-On.