Comments on: the next firefox business model

By: Chris Cunningham

Chris Cunningham — Tue, 24 Nov 2009 13:10:04 +0000

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

By: Al

Al — Mon, 23 Nov 2009 13:41:02 +0000

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.

By: Christopher Blizzard

Christopher Blizzard — Fri, 20 Nov 2009 20:03:03 +0000

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

By: bochecha

bochecha — Fri, 20 Nov 2009 13:45:33 +0000

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

By: Anonymous

Anonymous — Fri, 20 Nov 2009 08:44:54 +0000

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

By: Christopher Blizzard

Christopher Blizzard — Fri, 20 Nov 2009 06:23:11 +0000

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

By: Che Kristo

Che Kristo — Fri, 20 Nov 2009 05:31:07 +0000

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