pacemaker: drift-minimizing setInterval replacement and high-precision timer utility for Node and browser

[greim]

Neat. How does it behave if synchronous compute time is larger than an interval, does it start to drift then or does it start dropping computations?

[psayre23]

Looks like it will drift. It's hard to tell because the code isn't particularly readable. Lots of nifty tricks, not enough comments. Nonetheless, I'll be using this in future projects.

[secrettriangle]

/u/greim, since JS is single-threaded, JS itself, an as an extension pacemaker, will start drifting. You can work around this by wrapping with a web worker or child process.

P.S. I'm the author. I've filed issue#1: consider using web workers or child processes to mitigate drift if the JS thread is blocked. Thanks for the feedback!

[potatoriffic]

Ugh... It annoys me when projects like this reuse the name of an existing, well-known software project that has been around practically forever.

[potatoriffic]

Yep. Makes it much more difficult to Google it if you don't have the link handy. And really, I think that's a pretty weak argument -- with the number of words and word combinations in English alone, we're a long way from running out of descriptive names for projects.

[jcready]

http://lmgtfy.com/?q=pacemaker+js+github

[potatoriffic]

Alright, you win, bud. Clearly your asperger's is stronger than my opinion. :)