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.
-
Ah, the joys of running with no plugins at all. I can’t remember the last time I had Firefox crash.
-
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 comments
Comments feed for this article
Trackback link: http://www.0xdeadbeef.com/weblog/2009/11/the-next-firefox-business-model/trackback/