Adobe CTO on Flash for Mac
blogs.adobe.com
blogs.adobe.com
To a large degree, I agree with this choice, and I welcome Flash's demise (if it happens) in favor of something more open / capable / faster. Flash serves unique needs which have now largely been done better by other tools.
Apple is all about feel, and as they absolutely cannot control the quality of the flood of old / crappy flash apps that will grind the machine to a halt if they enable it, they've decided to block it outright. It fits perfectly with their App Store model, where they can ensure programs run quickly enough. Whether you agree with the App Store model or not is another issue entirely, Apple is being merely consistent in all this.
While Apple officially supports scripting WebKit and extends it ever deeper into iPhone OS APIs, I don't think they'll be willing to take on a similar venture with Adobe's Action Script.
On the other hand, I'm no apologist for Flash. I wish it would go away just as much as the next guy. My only worry is that annoying advertisements that I can currently block trivially using FlashBlock may later be implemented using JS, SVG, canvas, etc., and thereby become much much harder to block reliably.
Switching to Core Animation drawing (as in Flash Player 10.1) allows the plugin to draw directly to a backing store in video memory without having to wait for the browser. The plugin still has to request that the view be updated, but it's much faster as it can be done mostly on the GPU.
I'm not an expert on plugins or graphics, but that is how I understand it.
I can eat up 100% of your CPU with Python.
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.
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.
For Maemo, see earlier on Hacker News: http://news.ycombinator.com/item?id=1090855
(Noise & disinfo levels seem at all-time highs recently... Engadget may merely be the first site of many to adapt.)
Oh really? I've disabled Flash on all my browsers a week ago and don't even notice that I'm missing so much web-content!
I open a video site. I try to jump to a location in the middle of the video. It crashes.
And of course, if you play 3-4 videos, the MacBook will decide to switch itself off because of overheating.
/sarcasm
Crashing seems to be mostly directly correlated with pseudonymous Apple-polishing on webforums.... ;-)
(btw, if you're sincerely trying to improve your own experience, there's a quick set of diagnostics here: http://blogs.adobe.com/jd/2010/02/troubleshooting_player_sta... )
Like I said; no amount of effort on your part is going to make us forget our experiences with your suck ass plugin crashing our browser every day. Thankfully, there are Flash blocker plugins that make this a more rare event.
Your inability to understand this does explain why Flash is getting worse instead of better though. So thanks for that.