I haven't benched it in a while but as far as I know setTimeout and setInterval can have an extra delay depending on [what I call] browser pain. I measure this

I haven't benched it in a while but as far as I know setTimeout and setInterval can have an extra delay depending on [what I call] browser pain. I measure this delay to set the pace of computationally heavy tasks. I also consider it a proof of concept why browsers should expose more of the performance and capability stats to the web page. Maybe I don't want translucent layers of css animations if it freezes the gui? At least, I think I don't. Also funny: Because callbacks can trigger computationally heavy tasks that may trigger at the same time I've morphed into the habit of just slapping the data into an array and parsing it with a setTimeout used as a setInterval. So, basically I went back to polling because of superior performance. (ha-ha)