title: Bad smoothness webkitRequestAnimationFrame vs setInterval
body: <p>With regard to a <a href="https://stackoverflow.com/questions/5121326/how-to-implement-renderer-with-respect-to-cpu-capabilities">previous question</a> of mine, I tried out Chromium's support of <code>webkitRequestAnimationFrame</code>. Although it would have a bunch of advantages, it turned out to be much worse for me than using plain <code>setInterval</code> / <code>setTimeout</code> for generating an animation.</p>
  
  <p>I tried the example stated on <a href="http://paulirish.com/2011/requestanimationframe-for-smart-animating/" rel="nofollow noreferrer">http://paulirish.com/2011/requestanimationframe-for-smart-animating/</a>, both with <code>webkitRequestAnimationFrame</code> and with <code>setTimeout</code>:</p>
  
  <ol>
  <li><code>webkitRequestAnimationFrame</code>: <a href="http://jsfiddle.net/hnQYt/" rel="nofollow noreferrer">http://jsfiddle.net/hnQYt/</a></li>
  <li><code>setTimeout</code>: <a href="http://jsfiddle.net/hnQYt/2/" rel="nofollow noreferrer">http://jsfiddle.net/hnQYt/2/</a></li>
  </ol>
  
  <p>Am I the only person having issues with the smoothness of the first method? If not, how come this specially designed method fails miserably?</p>