Linked by Thom Holwerda on Wed 22nd Feb 2012 15:24 UTC, submitted by Ajeet
Multimedia, AV On my mark... Get set... Start not caring! Adobe has announced it plans to discontinue the stand-alone Flash Player for Linux, instead focussing all its effort on the version available through the Pepper API - which, besides Chrome, no one else is going to support.
Thread beginning with comment 508117
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE: Pepper for Firefox
by Erunno on Wed 22nd Feb 2012 17:05 UTC in reply to "Pepper for Firefox"
Erunno
Member since:
2007-06-22

I hope that this helps push Mozilla to reconsider their decision to reject Pepper


Practical and ideological reasons prevent Mozilla from adopting Pepper. Practical because Pepper is underspecified and only exists as a code blob and allegedly is full of Webkitisms which make it hard to integrate into other code bases. Ideological because Mozilla would rather improve the web platform and not invest developer resources into what they consider technology of the past.

Reply Parent Score: 11

RE[2]: Pepper for Firefox
by kaiwai on Thu 23rd Feb 2012 05:26 in reply to "RE: Pepper for Firefox"
kaiwai Member since:
2005-07-06

Practical and ideological reasons prevent Mozilla from adopting Pepper. Practical because Pepper is underspecified and only exists as a code blob and allegedly is full of Webkitisms which make it hard to integrate into other code bases. Ideological because Mozilla would rather improve the web platform and not invest developer resources into what they consider technology of the past.


Good - focus on the future whilst in the present your market is destroyed by those living in reality. Plugins are going to be with us for at least the next 5 years minimum so it is time one just got used to that fact and moved on.

As for the implementation - why do they have to whole sale 'copy and paste' code form webkit? why didn't they participate in the develop and implement themselves instead of relying on someone else's work? the complaining sounds like a person failing a test then blaming the person sitting next to them for not allowing them to copy their answers.

Edited 2012-02-23 05:26 UTC

Reply Parent Score: 2

RE[3]: Pepper for Firefox
by Erunno on Thu 23rd Feb 2012 08:16 in reply to "RE[2]: Pepper for Firefox"
Erunno Member since:
2007-06-22

Plugins are going to be with us for at least the next 5 years minimum so it is time one just got used to that fact and moved on.


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?

As for the implementation - why do they have to whole sale 'copy and paste' code form webkit? why didn't they participate in the develop and implement themselves instead of relying on someone else's work?


*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

Reply Parent Score: 6