• 0 Posts
  • 17 Comments
Joined 1 year ago
cake
Cake day: June 22nd, 2023

help-circle







  • locuester@lemmy.ziptoProgrammer Humor@lemmy.mlSTOP DOING ASYNC
    link
    fedilink
    English
    arrow-up
    1
    ·
    10 months ago

    I’m well aware how async works in the single threaded js environment. All code blocks the main thread! Calling await on an async operation yields back.

    You’re right, async is commonly mixed up with multi-threaded. And in fact in many languages the two things work hand in hand. I’m very aware of how it works in JavaScript.

    We are agreeing. Don’t need more info.


  • locuester@lemmy.ziptoProgrammer Humor@lemmy.mlSTOP DOING ASYNC
    link
    fedilink
    English
    arrow-up
    1
    ·
    10 months ago

    Yes I’m simplifying a LOT, but in the context of background web calls, that was what callbacks became so important for. XMLHttpRequest in IE 5 sparked the Ajax movement and adventures in nested callbacks.

    Prior to that, the browser had window.setTimeout and its callback for delays and animation and such - but that’s it.

    The main purpose of all this async callback stuff was originally, and arguably still is (in the browser), for allowing the ui event loop to run while network requests are made.

    NodeJS didn’t come into the picture for almost 10 years or so.