2 comments

[ 4.1 ms ] story [ 14.5 ms ] thread
Summary: the script shows advertisement, and adds a 4 second delay after that.

But the tweet is actually incorrect. setTimeout call does not use any "computation time" (or "cpu time" or "userspace time"). It does waste wall-clock time, but CPU can do other things at that time. As long as your machine has other things to do, nothing is wasted.

Thanks for pointing this out! The idea here was that CI/CD systems (such as self-hosted runners) charge for the wall-clock time.