News for hackers. Stuff that matters.
Re:Windows Timer Resolution: Megawatts Wasted by mischanix on Thursday July 11, 2013 @12:44AM (#6024498)
Right, but that precedent was only set by incorrect implementations existing in the first place. Using setTimeout(,0) recursively in lieu of (a then unavailable) requestAnimationFrame or a non-zero timeout period is in my mind equivalent to while(true){}/infinite tail recursion.
Re:Windows Timer Resolution: Megawatts Wasted by mischanix on Thursday July 11, 2013 @03:54AM (#6024939)
And yes, in the HTML5 spec (years later), it was standardized to a 4ms clamp, also because of the incorrect implementations prior.