I'm gett the ing UDP same vib joke

I PROMISE the rest will come eventually

You must .await before you can have the Result. Then you can use ?

If you are waiting for IO, why would you block your current thread and not let it do something else? Async does not only exist in JS.

After using both extensively I would argue async code is easier to read. It has a lot less nesting. And generally easier to read code is a good thing so I'm all for async.

A huge amount of time in apps is spent waiting for IO, database or web requests to complete.

Async prevents locking a thread during this wait.

If you're handling a large amount of requests in a web server, for example, it allows other requests to progress while waiting for these operations.

Threads are also expensive to start and manage.

Also handling threads manually is a pain in the ass.

Because the alternative is a series of ridiculously nested call backs that make code hard to read and manage?

I honestly can't fathom how anyone would dislike async programming.

Async is good because threads are expensive, might aswell do something else when you need to wait for something anyways.
But only having async and no other thread when you need some computation is obviously awful.. (or when starting anothe rthread is not easily manageable)

Thats why i like go, you just tell it you want to run something in parallel and he will manage the rest.. computational work, shift current work to new thread.. just waiting for IO, async.

Ok, I'm a c# developer and I use async await quite extensively. Is it different in JS? Or am I missing something?

Imagine a webser or proxy and for every incoming request it creates an new thread 💣

Yes you're right if it's a second or third thread it is/may be fine. But if you're i/o bound and your application has to manage quite a lot of that stuff in parallel, there is no way around delegating that workload to the kernel's event loop. Async/Await is just a very convenient abstraction of that Ressource.

Async rust with the Tokio Framework is pretty cool. Need none of that JS bloat for async.

async/await is just callback() and queueMicrotask wrapped up into a neat package. It's not supposed to replace multi-threading and confusing it for such is dangerous since you can still stall your main/UI thread with Promises (which async also wraps).

(async and await are also technically different things, but for the sake of simplicity here, consider them a pair.)

Observables are your friends

It's a meme, it's not actually saying not to use async:

https://knowyourmeme.com/memes/stop-doing-math