2020-04-16
3559
#vanilla javascript
Alexander Nnakwue
16959
Apr 16, 2020 ⋅ 12 min read

The evolution of asynchronous programming in JavaScript

Alexander Nnakwue Software engineer. React, Node.js, Python, and other developer tools and libraries.

Recent posts:

Catch Frontend Issues Before Users Using Chaos Engineering

Catch frontend issues before users using chaos engineering

This article covers how frontend chaos engineering helps catch UI and UX issues before users experience them using tools like gremlins.js.

Muhammed Ali
Jul 25, 2025 ⋅ 5 min read
what's new in deno 2.4

Deno 2.4 is here: What’s new and what to expect

Deno 2.4 isn’t just a maintenance update; it’s a statement. Learn about the most impactful changes in Deno 2.4, including the return of a first-party bundler and new spec-aligned ways to handle assets.

Ikeh Akinyemi
Jul 24, 2025 ⋅ 5 min read
Migrating Tanstack Start From Vinxi To Vite

Migrating Tanstack Start from Vinxi to Vite

Update your TanStack Start project from Vinxi to a Vite-based setup, including dependency adjustments and configuration file updates.

David Omotayo
Jul 24, 2025 ⋅ 6 min read
AI roundtable AI proof skills

What are the AI-proof skills every frontend developer needs?

The AI freight train shows no signs of slowing down. Seven senior developers discuss how frontend devs can make themselves indispensable in the age of AI.

Matt MacCormack
Jul 23, 2025 ⋅ 4 min read
View all posts

4 Replies to "The evolution of asynchronous programming in JavaScript"

  1. It’s mostly a good article, but please be rigorous and accurate, or you’ll confuse a lot of people.

    It’s untrue that function A doesn’t run inside function B. It does run, and a console.log() on the first line of A will prove that. Function A creates an anonymous function (the callback) and the body of the anonymous function is what doesn’t run until after B exits.

  2. Fyi the most important callback is the one fed directly into the asynchronous command offered by nodejs or the browser.

    For example, the “someFunction” in fs.readFile(url, someFunction). readFile is an asynchronous function (you’d just have to look it up or play with it to know that). It reads a file, then calls someFunction when it’s done.

    If it didn’t, none of this other stuff would matter. Most of this article is about clever ways to put what you desire into that “someFunction.” Including promises.

Leave a Reply