How to think about `async`/`await` in Rust

Re:How to think about `async`/`await` in Rust by atombender on Wednesday July 05, 2023 @02:22PM (#36604779)

This thread is about async/await, which was added to JavaScript in 2017. Before then, async programming was only done with Node.js (unless you consider windows.setTimeout() to be "event-driven programming"), which came out in 2009. Event-driven programming was an established paradigm years before then.

[ Parent | on HN ]

Re:How to think about `async`/`await` in Rust by munificent on Thursday July 06, 2023 @12:53PM (#36618966)

> This thread is about async/await, which was added to JavaScript in 2017.

The article is about async/await, but the comments I'm replying to seem to be about asynchronous programming in general. JS was doing async for many years before async/await was added.

[ Parent | on HN ]

Re:How to think about `async`/`await` in Rust by atombender on Thursday July 06, 2023 @01:11PM (#36619283)

Nobody was doing async JS before Node, which came long after async I/O was an established paradigm.

[ Parent | on HN ]

Re:How to think about `async`/`await` in Rust by munificent on Thursday July 06, 2023 @03:53PM (#36621845)

XMLHttpRequest shipped in 1999. AJAX was coined in 2005. The "A" in "AJAX" is for "asynchronous".

[ Parent | on HN ]

Re:How to think about `async`/`await` in Rust by atombender on Friday July 07, 2023 @04:28AM (#36628870)

XMLHttpRequest may be async, but it's not an asynchronous programming model.

[ Parent | on HN ]