5 ms·

Could it be that some crashes are the fault poor programming and not the Flash Player itself? I can eat up 100% of your CPU with Python.

by wensing 17y ago

rayboyd 17y ago
Actionscript in the right hands can perform very well. A big part of the problem lies with the barrier to entry (low) and the features available to developers and designers via its API and tool-set. Things like bitmap manipulation and real-time filters (drop-shadow, glow etc), they are really easy to implement and designers love the effects that can be achieved and tend to design with them in mind (can't blame them really), but without optimization care and skill it will eat a CPU alive. These effects can also be implemented without a single line of code, a lot of the time it is not even the developers at fault. I worked agency level for a number of years before I lost the will to live and gave it up, I seen this kind of thing daily and the culture of getting it out there didn't help either, unless there was a really switched on PM or lead developer in charge who understood this optimization time was generally second class. EDIT: it did not help that OSX was a second class citizen and Flash took a 15% hit in Firefox (windows) either.
tlrobinson 17y ago
Flash video performanc is awful on OS X and Linux. That is entirely Adobe's fault.
- deleted 17y ago
  [deleted]
- godDLL 17y ago
  An Intel Core2 Duo Mac Mini, with no graphics card to speak of (so this couldn't skew the results even theoretically) plays 720p H.264 YouTube-encoded videos with ~9% CPU usage, and no hiccups, the frame-rate is evenly distributed, every frame lasts for whatever time it should. Compare and contrast with the Flash decoder, that ceilings at about 70%, and plays un-evenly, even on a frame-by-frame level -- there is no way of telling how much time a given frame is showing on the screen. That's why many will use Rentzsch' Click-to-Flash WebKit plug-in, to block all Flash permanently and play H.264 movies natively. github.com/rentzsch/clicktoflash Here's another one, this time from Firefox for Maemo RC3: > We’ve decided to disable plugin (not to be confused with add-ons, which are supported) support for this release. The Adobe Flash plugin used on many sites degraded the performance of the browser to the point where it didn’t meet our standards.
  - jdowdell 17y ago
    Sounds like didn't read the linked info either. For Maemo, see earlier on Hacker News: http://news.ycombinator.com/item?id=1090855 http://news.ycombinator.com/item?id=1090855
po 17y ago
…but my web browser doesn't run python.
- wensing 17y ago
  I can eat up 100% of your CPU with JavaScript.

Could it be that some crashes are the fault poor programming and not the Flash Player itself? I can eat up 100% of your CPU with Python.

by wensing 17y ago

Could it be that some crashes are the fault poor programming and not the Flash Player itself? I can eat up 100% of your CPU with Python.

rayboyd 17y ago

Actionscript in the right hands can perform very well. A big part of the problem lies with the barrier to entry (low) and the features available to developers and designers via its API and tool-set. Things like bitmap manipulation and real-time filters (drop-shadow, glow etc), they are really easy to implement and designers love the effects that can be achieved and tend to design with them in mind (can't blame them really), but without optimization care and skill it will eat a CPU alive. These effects can also be implemented without a single line of code, a lot of the time it is not even the developers at fault. I worked agency level for a number of years before I lost the will to live and gave it up, I seen this kind of thing daily and the culture of getting it out there didn't help either, unless there was a really switched on PM or lead developer in charge who understood this optimization time was generally second class. EDIT: it did not help that OSX was a second class citizen and Flash took a 15% hit in Firefox (windows) either.

tlrobinson 17y ago

Flash video performanc is awful on OS X and Linux. That is entirely Adobe's fault.

deleted 17y ago
[deleted]
godDLL 17y ago
An Intel Core2 Duo Mac Mini, with no graphics card to speak of (so this couldn't skew the results even theoretically) plays 720p H.264 YouTube-encoded videos with ~9% CPU usage, and no hiccups, the frame-rate is evenly distributed, every frame lasts for whatever time it should. Compare and contrast with the Flash decoder, that ceilings at about 70%, and plays un-evenly, even on a frame-by-frame level -- there is no way of telling how much time a given frame is showing on the screen. That's why many will use Rentzsch' Click-to-Flash WebKit plug-in, to block all Flash permanently and play H.264 movies natively. github.com/rentzsch/clicktoflash Here's another one, this time from Firefox for Maemo RC3: > We’ve decided to disable plugin (not to be confused with add-ons, which are supported) support for this release. The Adobe Flash plugin used on many sites degraded the performance of the browser to the point where it didn’t meet our standards.
- jdowdell 17y ago
  Sounds like didn't read the linked info either. For Maemo, see earlier on Hacker News: http://news.ycombinator.com/item?id=1090855 http://news.ycombinator.com/item?id=1090855

po 17y ago

…but my web browser doesn't run python.

wensing 17y ago
I can eat up 100% of your CPU with JavaScript.