News for hackers. Stuff that matters.
Re:Adobe, Apple, and Flash by ericd on Monday January 25, 2010 @01:01PM (#1075652)
The Mac implementation of the Flash player is awful, it regularly pegs my CPU. I'm assuming that HTML 5 in a well coded browser will not do the same, no matter how annoying the ad.
Re:Adobe, Apple, and Flash by Groxx on Monday January 25, 2010 @01:48PM (#1075779)
If you're talking Youtube's HTML5 video player, I regularly stay below 20% CPU. That's 10% total power, as percentages go above 100 when using more than one core.

Otherwise, it'd be Javascript + <canvas>, which so far is pretty darned fast, but not too friendly to ad-servers. Not Flash-fast, but speedy, and quickly getting faster. If JS+canvas gets more popular, you can bet that JS will get WAY more attention in this area.

Re:Adobe, Apple, and Flash by cake on Monday January 25, 2010 @02:30PM (#1075891)
I'm actually quite disapointed by Youtube's HTML5. I had great expectations, I know it's just the beginning and I'm sure it'll be better, but I'm closer to 80% CPU than 20% with my Macbook on Safari 4.
Re:Adobe, Apple, and Flash by tl on Monday January 25, 2010 @06:20PM (#1076524)
On Ubuntu 9.10(all same video):

Youtube HTML5 - 15-20% CPU

Youtube Flash - 20-25% CPU

.flv in Totem - 2-3% CPU

Clearly, there is optimisation work needed here.

Re:Adobe, Apple, and Flash by Groxx on Monday January 25, 2010 @05:07PM (#1076353)
That could explain it. I'm on a MBP, with 10.6, so I may be getting the hardware decoding, while you're not.
Re:Adobe, Apple, and Flash by notauser on Monday January 25, 2010 @02:12PM (#1075839)
Any kind of JavaScript while(true) loop will lock up the page, so you aren't safe from incompetent coders just yet. Depending on the browser and the OS that can bog down the CPU as badly as Flash.

(And there's no move towards parallel execution of in-page dom-touching JavaScript yet - web workers can't do it. Concurrency is such an issue that you can't even pass a function into a web worker in case it has bound variables - it's separate-script-and-message-passing only.)