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.
Permalink for comment 508240
To read all comments associated with this story, please click here.
RE[5]: Pepper for Firefox
by Erunno on Thu 23rd Feb 2012 14:01 UTC in reply to "RE[4]: Pepper for Firefox"
Erunno
Member since:
2007-06-22

Safari already supports NPAPI pepper extensions which is why Flash was able to use hardware acceleration frameworks such as Core Animation, Core Image etc. for their Apple plugin.


Since version 10.1 Flash uses CoreAnimation and a bunch of other OS X frameworks to implement part of its functionality like drawing. How does NPAPI (pepper or not) plays into it exactly? Citation for your claims please. Here's an article from a Flash engineer and it doesn't say anything about NPAPI (pepper or not): http://www.kaourantin.net/2010/02/core-animation.html

The original Mozilla Pepper wiki entry listed all the contributions by Apple


https://wiki.mozilla.org/index.php?title=NPAPI:Pepper&oldid=275848

Where exactly? This the last version before the page was blanked.

Don't be surprised if Dart ends up in Safari soon


Actually, I would since Apple's WebKit engineers flat out refused to accept the necessary changes to support Dart just a few weeks ago. Google wanted to make WebKit language-agnostic and allow multiple concurrent scripting engines (currently only JavaScript is supported and only one engine at a time). Part of the reason for the refusal was the added code complexity and therefore maintenance burden. Another part was that Dart is not a web standard and WebKit's own mission statement says "[...] using standards-based technologies such as HTML, CSS, JavaScript and the DOM" and they want to avoid adding to the current fragmentation.

I'm not saying that Dart in WebKit might not happen at one later point if the decision of the engineers is overridden by higher management but currently the magic eight ball says "Unlikely".

For over 10 years I've seen Firefox developers neglect the Mac platform


Windows Vista/7 users had to endure a very non-native looking interface until just recently (Firefox 4) so it's not like OS X is the only one suffering from that, especially if you consider that most developers are apparently using Mac or Linux. It simply boils down to lack of manpower, especially since large parts of Firefox codebase is currently being rewritten.

so quite frankly long term dimise of Firefox doesn't fill me with any grief.


Which is unfortunate and very short-sighted since Mozilla is the only organization which believably fights for an open web. Whatever organizational failures Mozilla displayed in the past (and there were far too many), at least they got their priorities straight.

When arrogant programmers refuse to acknowledge that their product leaks memory like a sieve then again I have no sympathy for them.


I can't really argue against this. Even if taking into account that most of the remaining leaks are caused by extensions, Mozilla was far too lenient for far too long towards misbehaving extensions despite using them as a unique selling point for Firefox. Classical case of wanting to keep their cake and eat it. At long last they are tightening their rules for extensions to be hosted by Mozilla and started developing tools to help developers with finding leaks.

Edited 2012-02-23 14:03 UTC

Reply Parent Score: 5