[ close ]
Help Upgrade the Web: Download Firefox 3.5

the next firefox business model

If you want to use our plugin APIs you have to sign an agreement that says anytime a user crashes because of your software, you pay us a nickel.  We wouldn’t have funding problems for a while, but boy would Adobe’s shareholders be pissed.

  1. Che Kristo’s avatar

    Inversely you have to ask, why can a plugin bring down the entire application?

  2. Christopher Blizzard’s avatar

    That’s why we’re going as fast as we can to get out of process plugins into 3.7.

  3. Anonymous’s avatar

    Ah, the joys of running with no plugins at all. I can’t remember the last time I had Firefox crash.

  4. bochecha’s avatar

    Isn’t nspluginwrapper supposed to run plugins in their own separate processes (npviewer.bin) ?

  5. Christopher Blizzard’s avatar

    Sure, but nspluginwrapper covers about 0.1% of our userbase.

  6. Al’s avatar

    Would the introduction of oop plugins not be a good time to rename it the “deprecated plugins interface”? In between things that should be replaced by audio and video tags (Flash, QuickTime, WMP), things that should be replaced by canvas and WebGL (Flash, Silverlight, Java), things that just launch desktop apps (Java Web Start, .Net too?), things that are so bloated they make their own gravity (Adobe Reader) and things that hope to screw the web one way or another (Flash, Silverlight) … well, basically, in the medium term they should all go away.

    The whole idea of plugins comes from a time before an open source browser and before powerful extensions, but seems much less relevant now.

  7. Chris Cunningham’s avatar

    It is kind of awesome that after having used an Acrobat browser plugin for ten years now, said plugin is still capable of readily crashing my browser simply by browsing to a PDF and scrolling about a bit, the single use case for the thing.

    – Chris