The specific pain point we ran into was a security consideration: my company needed to sign and distribute a private internal extension whose code betrayed the

The specific pain point we ran into was a security consideration: my company needed to sign and distribute a private internal extension whose code betrayed the layout of an internal API. The signing process for stable Firefox requires uploading the extension to AMO, which our management was not crazy about. Sure, anyone can technically do it, but the dependence on a third party service is still there. Ultimately we decided to do it anyway, figuring that the cost of having our support floor run a non-stable browser outweighed the risk of a code leak at Mozilla. But the whole process left a bad taste. I get where they're coming from, really I do. Malware is a huge problem and the average user has zero clue how to vet extension code. I dunno, I have mixed feelings about the solution. I'm not sure if there's a middle ground to be had.