Hacker News Reader

You must have heard wrong, and it's the other way around.

Apple did not open their video acceleration APIs until they released OS X 10.6.3 circla mid-2010.

http://xbmc.org/davilla/2010/05/03/osx-gets-h-264-accellerat...

If that's the major reason preventing them from being performant, then I misunderstood the reason for crashing and the reason for poor performance to be the same. Apple should not be complaining about CPU usage.

That doesn't excuse Adobe from making buggy plugins.

Indeed the flash plugin has been riddled with crashers and security vulnerabilities. But the blame for high CPU usage during video decoding seems to have been mostly in Apple's court before that.

With Mountain Lion 10.8 Flash is still the same like before those APIs were released. I think Adobe just don't cares about it. I really I can't the strategy behind it. Flash at its best times was nearly on every PC and Mac why is that they didn't want to improve the quality of their app.

I don't want to listen (to customers and developers) you need to feel it.

Even without that API 10.6.2 and before video players still used a lot less CPU when decoding video.

Worse yet, nothing stops flash from working in the YUV color space when mixing video and non video elements.

Reply on news.ycombinator.com