Linked by Thom Holwerda on Wed 22nd Feb 2012 15:24 UTC, submitted by Ajeet
Permalink for comment 508211
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 05/19/13 23:15 UTC
Linked by Thom Holwerda on 05/19/13 23:11 UTC, submitted by Drumhellar
Linked by Thom Holwerda on 05/18/13 21:06 UTC
Linked by Thom Holwerda on 05/18/13 7:37 UTC
Linked by fran on 05/18/13 1:38 UTC
Linked by Thom Holwerda on 05/17/13 23:35 UTC, submitted by kragil
Linked by MOS6510 on 05/17/13 22:22 UTC
Linked by Thom Holwerda on 05/17/13 22:15 UTC, submitted by Tom
Linked by Thom Holwerda on 05/16/13 21:41 UTC
Linked by Thom Holwerda on 05/16/13 17:04 UTC
More News »
Sponsored Links



Member since:
2007-06-22
That's why Mozilla is still supporting NPAPI. None of the other browser vendors (including Apple) have signaled any interest in supporting Pepper currently. Mozilla might rethink their position if market pressure demands it (i.e. they are the last non-supporting browser). Right now I don't see the necessity. Flash is still supported via NPAPI on important platforms like Windows and OS X which makes up the majority of their users.
And what other NPAPI plug-ins of note are currently required regularly apart from Flash and occasionally Java for the odd banking site?
*ring ring* 2011 called and would like to talk to you about Dart. Apparently Google isn't as interested in cooperative standards development anymore as they used to. Pepper, like Dart, was also devised and developed at Google in secret and was presented to the public after they had a mostly working system. And unlike a prototype which is used as a basis to start standardization discussion (including the option to make radical changes or discard the offer altogether) Google is already using Pepper in production systems so the opportunities for others to participate are rather narrow.
Edited 2012-02-23 08:17 UTC