3 ms·

Doubly so if your product crashes even half as often as Flash. That they cannot seem to code for stability doesn't give me any confidence in their ability to co

by pi18n 14y ago

Doubly so if your product crashes even half as often as Flash. That they cannot seem to code for stability doesn't give me any confidence in their ability to code for speed. I heard that they refused to work with Apple to improve its performance on Mac, and that was a core reason why they got excluded from the iOS platform -- searching for this I came up with an explanation directly from Apple: "Symantec recently highlighted Flash for having one of the worst security records in 2009. We also know first hand that Flash is the number one reason Macs crash. We have been working with Adobe to fix these problems, but they have persisted for several years now. We don’t want to reduce the reliability and security of our iPhones, iPods and iPads by adding Flash."

0x0 14y ago
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-accelleration/ http://xbmc.org/davilla/2010/05/03/osx-gets-h-264-accellerat...
- pi18n 14y ago
  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.
  - 0x0 14y ago
    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.
    - oemera 14y ago
      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.
- Retric 14y ago
  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.
luriel 14y ago
> That they cannot seem to code for stability doesn't give me any confidence in their ability to code for speed. Much more importantly, it doesn't give me any confidence in their ability to code for security.
novalis 14y ago
That quote is a great piece of PR. The number one reason quoted from that Symantec report was: "Microsoft Windows SMB Remote Code Execution". It also didn't have anything to do with what makes Macs crash, it was a report on vulnerability per plat, it mentioned flash in cross site exploits, not flash by itself. But to this day and for a long time the music keeps playing. Here is a good analysis of that text that explains a lot on how that statement is great PR but nothing more: http://truegryc.blogspot.pt/2010/05/response-to-thoughts-on-flash.html http://truegryc.blogspot.pt/2010/05/response-to-thoughts-on-...

by pi18n 14y ago

0x0 14y ago

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-accelleration/ http://xbmc.org/davilla/2010/05/03/osx-gets-h-264-accellerat...

pi18n 14y ago
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.
- 0x0 14y ago
  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.
  - oemera 14y ago
    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.
Retric 14y ago
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.

luriel 14y ago

> That they cannot seem to code for stability doesn't give me any confidence in their ability to code for speed. Much more importantly, it doesn't give me any confidence in their ability to code for security.

novalis 14y ago

That quote is a great piece of PR. The number one reason quoted from that Symantec report was: "Microsoft Windows SMB Remote Code Execution". It also didn't have anything to do with what makes Macs crash, it was a report on vulnerability per plat, it mentioned flash in cross site exploits, not flash by itself. But to this day and for a long time the music keeps playing. Here is a good analysis of that text that explains a lot on how that statement is great PR but nothing more: http://truegryc.blogspot.pt/2010/05/response-to-thoughts-on-flash.html http://truegryc.blogspot.pt/2010/05/response-to-thoughts-on-...