Linked by Thom Holwerda on Thu 11th Mar 2010 22:59 UTC
Benchmarks Common wisdom has it that Flash is a resource hog, and that HTML5 will prevent your processor from having to work really, really hard to show animations of videos. Well, a number of people have conducted benchmarks with the latest browsers and Flash betas, and common wisdom is starting to show serious signs of crackage.
Thread beginning with comment 413333
To read all comments associated with this story, please click here.
Regarding Apple
by kaiwai on Fri 12th Mar 2010 00:20 UTC
kaiwai
Member since:
2005-07-06

Regarding Apple; nothing has ever stopped Adobe from hooking into QuickTime and using the Apple h264 codec instead of their own built in one. The offer is there, and I am sure if they did that for an iPod/iPhone version instead of their own codec the problems would be eliminated with the only ones remaining being a matter of either optimising the scripting engine or blaming Apple for inefficient QuickTime.

Adobe could do that, but they choose not to, just like Adobe could have gradually ported their applications from Carbon to Cocoa over 10 years - yes you can mix Carbon and Cocoa together. Adobe could have done that, but like the Flash issue, they didn't. So for me, I don't have the slightest sympathy for Adobe.

To add further proof to what I said, Silverlight doesn't have any of the reliability, stability or speed that Flash has. The excuse of Adobe is more about excusing incompetent programmers - and worse, anyone remember the claim, "we don't ship Flash with known crashes" and yet there was a bug unfixed for 18 months!

Edited 2010-03-12 00:26 UTC

Reply Score: 5

RE: Regarding Apple
by elanthis on Fri 12th Mar 2010 01:32 in reply to "Regarding Apple"
elanthis Member since:
2007-02-17

Adobe can't do anything on the iPhone. It has nothing to do with technical limitations, it has to do with Apple banning any app from downloading and executing external code. Even native iPhone apps run into tricky areas regarding the use of scripting languages and the like. Apple is not really that friendly to developers on the iPhone.

Reply Parent Score: 2

RE: Regarding Apple
by Nelson on Fri 12th Mar 2010 01:56 in reply to "Regarding Apple"
Nelson Member since:
2005-11-29


To add further proof to what I said, Silverlight doesn't have any of the reliability, stability or speed


[citation needed].

Reply Parent Score: 2

RE[2]: Regarding Apple
by kaiwai on Fri 12th Mar 2010 02:41 in reply to "RE: Regarding Apple"
kaiwai Member since:
2005-07-06

"
To add further proof to what I said, Silverlight doesn't have any of the reliability, stability or speed


[citation needed].
"

It is pretty damn obvious that it was a mistake; it should have said, "Silverlight doesn't have any of the reliability, stability or speed issues that flash has". You can thank the crappy forum for the lack of being able to edit posts after 20 minutes for the mistake.

Reply Parent Score: 3

RE: Regarding Apple
by wargum on Fri 12th Mar 2010 12:55 in reply to "Regarding Apple"
wargum Member since:
2006-12-15

Regarding Apple; nothing has ever stopped Adobe from hooking into QuickTime and using the Apple h264 codec instead of their own built in one.

I think it is fair to say that neither you nor me can really know whether that is actually true or if QT would be actually suitable for that particular situation.

inefficient QuickTime.

Which is kind of true. To date, only NVIDIA 9400M can decode H.264 through QuickTime, what a shame.

Adobe could do that, but they choose not to, just like Adobe could have gradually ported their applications from Carbon to Cocoa over 10 years

Hah! One sided views make the world seem so easy! Guess what, even Apple hasn't ported all of their own apps over to Cocoa! Some prominent examples are iTunes and Final Cut Express/Pro.

and worse, anyone remember the claim, "we don't ship Flash with known crashes" and yet there was a bug unfixed for 18 months!

This one slipped through and they apologized for it.

Reply Parent Score: 2

RE[2]: Regarding Apple
by kaiwai on Fri 12th Mar 2010 19:51 in reply to "RE: Regarding Apple"
kaiwai Member since:
2005-07-06

This one slipped through and they apologized for it.


Bullcrap; when they shipped 10.0 they knew about the bug and claimed that development was too far along to fix it up; many updates over the 18 months since its release and not a single one of them addressed the bug. So please, stop the crap - Adobe knew they were shipping a product with a known crash bug and for 18 months chose to do nothing about it just like they could do something about the appalling CPU hogging of Flash but instead decides to blame everyone else for their incompetency.

Adobe should be thanking their lucky stars for the fact that if it weren't for Microsoft's stupid stance of not providing Silverlight development tools for Mac - Flash would have been strangled and left for dead by most developers years ago.

Edited 2010-03-12 19:52 UTC

Reply Parent Score: 2