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.
-
Archives
- May 2011
- April 2011
- March 2011
- December 2010
- October 2010
- August 2010
- July 2010
- June 2010
- May 2010
- April 2010
- March 2010
- February 2010
- January 2010
- December 2009
- November 2009
- October 2009
- September 2009
- August 2009
- July 2009
- June 2009
- May 2009
- April 2009
- March 2009
- February 2009
- January 2009
- December 2008
- November 2008
- October 2008
- September 2008
- August 2008
- July 2008
- June 2008
- May 2008
- April 2008
- March 2008
- February 2008
- January 2008
- December 2007
- November 2007
- October 2007
- September 2007
- July 2007
- June 2007
- May 2007
- April 2007
- March 2007
- February 2007
- January 2007
- December 2006
- November 2006
- October 2006
- September 2006
- August 2006
- July 2006
- June 2006
- May 2006
- April 2006
- March 2006
- February 2006
- January 2006
- December 2005
- November 2005
- October 2005
- September 2005
- August 2005
- June 2005
- May 2005
- April 2005
- February 2005
- January 2005
- December 2004
- November 2004
- October 2004
- September 2004
- August 2004
- July 2004
- June 2004
- May 2004
- April 2004
- March 2004
- February 2004
- January 2004
-
Meta
Inversely you have to ask, why can a plugin bring down the entire application?
That’s why we’re going as fast as we can to get out of process plugins into 3.7.
Ah, the joys of running with no plugins at all. I can’t remember the last time I had Firefox crash.
Isn’t nspluginwrapper supposed to run plugins in their own separate processes (npviewer.bin) ?
Sure, but nspluginwrapper covers about 0.1% of our userbase.
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.
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