Oddly, it use 100% of one of my i7 iMac core when running on Chrome (6.0.408.1). However, the animation play very smooth with only 1~2% CPU usage when running on Safari (4.0.5 6531.22.7).
So I assume you're using Chrome?
Edit: -webkit-animation in general seems to be very slow in Chrome.
Odd. Desktop iMac, older Core 2 version, it only takes me from my background 2% cpu use to 7% cpu use. Perhaps it is making heavy use of the GPU, which I wouldn't see in the cpu usage stats. (I add: using Safari.)
It looks like only Apple has hooked up WebKit animation to an underlying Core Animation-equivalent layer in the OS which uses the GPU for most of the hard work.
Not sure if Google is really motivated to do this kind of system-specific work in Chrome beyond the basic port.
I would argue that they should be. CSS is well understood by designers/programmers and doing animations all in JS is error prone and off course a CPU hog. Hardware acceleration is particularly important when you're talking about devices with underpowered CPUs (Android). On my iPad/iPhone CSS animations outperform JS animations by a ridiculous margin.
Just to clarify, they do have the CSS-based animations, since they're WebKit-based, but they're just not hooked up to an underlying hardware-based implementation.
I wasn't referring to the implementations, but this new wave of CSS3/HTML5 demos doing nothing that could solve a real-world problem.
Sure, I'd like all browsers to have a correct implementation of this technologies, I'm just questioning this type of demo. In the end they are just a fancy ACID-like test and frankly, we already have more than enough for this use.
This is a great demonstration of why to use CSS3 animations - Flash doesn't support the concept of graceful degradation. This page turns into a static image in Firefox/Mac instead of borking out with a blue lego piece.
I really appreciate the effort that has gone into building the demo. But i disagree with you.It is extremely easy for developers to provide fallback content when Flash is not availble.
As a developer, here is why i(personally) wont choose CSS3 animations for building similar content anytime in the near future:
-Works only on webkit browsers
-Performance is really bad on Chrome. Compared to most of the heavy weight flash content out there, this is just a very basic animation.
"It is extremely easy for developers to provide fallback content when Flash is not availble."
Really? How? I was an actionscripter for years before I dropped Flash from my arsenal and worked at a game company that would've loved to provide their games on systems without Flash.
I'm not sure I would call it smooth in Chrome on Windows 7, and this is on a gaming PC (more or less). The process was also using 25% CPU, which I believe Process Explorer would report as one full core.