For these types of questions, it is often useful to just go look at how node.js handles timers in the source code. What you will find is that node.js keeps one or more linked lists of its own internal timer objects and all timers set to occur at the same time share one libuv timer. … Read more
JavaScript is single-threaded. If some block of code uses execution thread, no other code can be executed. This means your setTimeout() call must wait until main execution (the one with busy-waiting while loop) finishes. Here is what happens: you schedule setTimeout() to execute after a second and then block main thread for 3 seconds. This … Read more
As far as I’ve tested, it just stops and resumes after the computer wakes up. When the computer awakes the setInterval/setTimeout is unaware that any time passed. I don’t think you should rely on the accuracy of setTimeout/Interval for time critical stuff. For google chrome I discovered recently that any timeout/interval (that is shorter than … Read more
The reason setInterval is bad is because it will try to execute the code every X MS regardless of what’s going on in the thread. So if you have: setInterval( complexFunction, 1 ); // complexFunction takes >1 MS to complete …you may end up with setInterval trying to re-execute several times before even its own … Read more
Yes, the message queue will have higher importance than timeouts one, and will thus fire at higher frequency. You can bind to that queue quite easily with the MessageChannel API: let i = 0; let j = 0; const channel = new MessageChannel(); channel.port1.onmessage = messageLoop; function messageLoop() { i++; // loop channel.port2.postMessage(“”); } function … Read more
I think what you posted explains itself really. Use .delay() for jQuery effects including animations. setTimeout() is best used for everything else. For example when you need to trigger an event at a certain elapsed time.
The setInterval method returns a handle that you can use to clear the interval. If you want the function to return it, you just return the result of the method call: function intervalTrigger() { return window.setInterval( function() { if (timedCount >= markers.length) { timedCount = 0; } google.maps.event.trigger(markers[timedCount], “click”); timedCount++; }, 5000 ); }; var … Read more
Just for the record, there is a way to get the time left in node.js: var timeout = setTimeout(function() {}, 3600 * 1000); setInterval(function() { console.log(‘Time left: ‘+getTimeLeft(timeout)+’s’); }, 2000); function getTimeLeft(timeout) { return Math.ceil((timeout._idleStart + timeout._idleTimeout – Date.now()) / 1000); } Prints: $ node test.js Time left: 3599s Time left: 3597s Time left: 3595s … Read more
The problem is here: setTimeout($scope.clickFilter(), 1000); Putting () after the function reference means that you want the function to be called, immediately, at that point in the code. What you probably want instead is something like: setTimeout($scope.clickFilter.bind($scope), 1000); which will pass a function reference to setTimeout(), as is required, and ensure that the function will … Read more
let timer: ReturnType<typeof setTimeout> = setTimeout(() => { … }); clearTimeout(timer); By using ReturnType<fn> you are getting independence from platform. You won’t be forced to use neither any nor window.setTimeout which will break if you run the code on nodeJS server (eg. server-side rendered page). Good news, this is also compatible with Deno!