The new requestAnimationFrame proposal is going to be a big thing for animation on the web going forward. Read up on it now if you’re a web developer. And if you are, also heed the unwritten warning at the end of the post:
In the forthcoming Chrome 11 release, we plan to reduce CPU consumption even for pages that are using setTimeout and setInterval. For background tabs, we intend to run each independent timer no more than once per second.
In other words: check to make sure your timers won’t break any site functionality if they get executed at a browser-enforced one-per-second interval.