incrediBILL - 11:33 am on Jun 7, 2012 (gmt 0)
My FF 12 just auto-updated to FF 13 so this thread is old new ;)
if I'm relying on a FF extension during a project, I don't want to chance it will be disabled by an update... and I generally don't want to take time to check out how long my current extensions are predicted to work.
Having your computer security held hostage over an add-on is a bad strategy.
Imagine some flaw in the browser allows your computer to get seriously hacked and you could have way more trouble on your hands than a disabled add-on, such as compromised server passwords, your machine being involved in a botnet spamming and hacking other computers, etc. etc.
Try explaining to your customer that your computer got hacked because you refused to update until his project was complete because you were afraid some FF SEO add-on might not work and now the machine is out at Geek Squad and may not come back for days or weeks and "... oh BTW, your FTP passwords were probably compromised..." or worse.
The next sound you hear will be the sound of his check bouncing off your bank account as he has the bank put a stop payment on it.
Not that there's anything wrong with using FF add-ons to do your work, I would just make sure I have a backup plan that will get the same job done in the event they no longer exist. I've been burned by a few add-on developers that literally just drop the ball and don't do timely updates to base a business strategy around any of them. If you can find any other alternate way to do the job, besides a FF add-on, I would opt for that route before banking on a single FF add-on. If you can't find anything, perhaps ask some developer your know to build it because others may be seeking an alternate solution as well, you never know!
But that's just me, YMMV.