`setTimeout()` Is NOT Part of JavaScript
On May 8th, a Dev.to post made a claim that sounds wrong until you check, and then sounds obvious: `setTimeout()` is not actually part of JavaScript. Not in the ECMAScript specification, the document that defines what the language is and does. Search it carefully and the function simply isn't there. What you find instead is that browsers implement it through the Web APIs layer — the same environment that gives you `fetch`, `document`, and `localStorage`. Node.js provides its own compatible version through its runtime. Both implementations behave similarly enough that most developers have spent entire careers assuming `setTimeout()` was a native language feature, as fundamental as `Array.map()` or a `for` loop. It isn't. It's infrastructure dressed up as language.
If confirmed — and the underlying technical reality here is not seriously in dispute, whatever you make of its significance — this matters more for education than for production code. Every developer who learned JavaScript through tutorials absorbed a mental model where the language and its host environment were essentially the same thing. They weren't. The distinction between what ECMAScript specifies and what browsers or runtimes provide is the same distinction that explains why `setTimeout()` behaves slightly differently across environments, why Web Workers don't have the full browser API, and why Deno made deliberate choices about which Web APIs to include. Getting this wrong doesn't break applications. It does produce engineers who struggle to reason about execution context, async behavior, and environment portability — problems that surface quietly and expensively in complex systems.
Watch for responses from educators and curriculum designers, or any pushback from the JavaScript community that either sharpens or complicates the original claim — either would move this story from background toward something worth revisiting in depth.
<p>JavaScript is often called <strong>single-threaded</strong>.</p> <p>That means it has one main thread and can execute <strong>one piece of JavaScript at a time</strong>.</p>
<p>TL;DR: setTimeout(fn, 0) doesn't run code instantly — it defers execution to the Macrotask queue, after all Microtasks and pending renders. Here's why relying on it is an
<h2> Introduction </h2> <p>Hey there, fellow coders! <br /> Imagine this: You’re at your favorite café, ordering a latte. The barista takes your order, but instead of starting on
NewsHive monitors these sources continuously. All signal titles above link to the original reporting.
Intelligence by NewsHive. Need help navigating what this means for your business? Contact GeekyBee →