#await — Public Fediverse posts

So the caller must await too. Ah no, rather return-immediately-with-a-fucking-promise. And so the caller's caller too and so on.

Now you hardly have a function call not preceded by await. Ask yourself: why is that not the default? For the other case, lets invent the keyword **getlost** to get the functionality we now have if we forget await.

😡 Sorry for venting. It is a relief.

#javascript #typescript #async #await #asyncawait

Because that's what it actually is. It does not wait at all. Quite contrary, it returns immediately, throwing the rest of the function code into a pool of stuff to be executed some day.

And the caller? Getting control back before things are really done? Without extra tooling the dev easily misses that the called async did exactly nothing and lets proceed the code as if. Fail!

2/n

#javascript #typescript #async #await #asyncawait

TypeScript is fun, but often I hate the JavaScript async/await crap.

Background: https://journal.stuffwithstuff.com/2015/02/01/what-color-is-your-function/

Async is like mold spreading through the code base. On top of it: why is it called **await** and not **return-immediately-with-a-fucking-promise**? ...

1/n

#javascript #typescript #async #await #asyncawait