Redpill me on async/await

It seems forced and unnecessary in 96% of the cases I find

map + join

https://dis.tinychan.net/read/prog/1616089645

does anyone actually understand async/await?

"callback hell"

callbacks are always much faster than any "event-based" polling which is async
ultimately is: async is only performant in optimized, compiled back-end code
that you want to scale, not client-side scripts.

>>4
PS I am anus

Eelsill me on ahorse/afucker

>>6 I meant to type

"Eelspill me on ahorse/afucker"

Admin-san please do the needful Sir.

>>7
edit your post

Async and await are useful in JavaScript. Callbacks are fine for simple cases, but suck when you need to compose asynchronous operations. Using promises (futures) directly also sucks, because you end up duplicating all the language's normal control flow operators in this shitty, baroque DSL (think

then()

,

catch()

,

finally()

, etc). You also have to follow a bunch of annoying coding patterns to guard against accidentally returning non-promise values, throwing synchronous exceptions, etc.

async

and

await

take away some of this pain. You can pretty much write code in the obvious manner, and it'll it work asynchronously under the hood.

Yeah it's fucking disgusting and should be hidden away at the framework/library/OS level.

AFAIK, it's only benefit is on say large cloud environments where you want to rinse as much from each instance as possible.

If you need to think about threading, your language is a failure.
Embrace golang.

Golang had a golden opportunity but was ruined by Unixfags chained to an obsolete C tradition. Sad!

>>12
That tradition works. Why break it?

>>13
It's too white

>>14
It's not white enough.

>>15
Your sickly yellow cum is a matter between you and your proctologist.