Perhaps it's common knowledge to JavaScript programmers but async and await are not general purpose coroutines, that is to say, an async function does not necessarily suspend execution on each await in the sense of unblocking the main event loop. This is because Promises run on the "microtask queue" and the browser will keep running them until there are no more left before it goes back to doing important things like responding to user input: https://developer.mozilla.org/en-US/docs/Web/API/HTML_DOM_API/Microtask_guide#microtasks
Obviously if you launch a bunch of async functions or Promises they will yield to each other but that is not actually what you want in most cases.
Concretely this means that using async for CPU-bound APIs is considered harmful (tm). So we have to remove async from most functions in the API.
Conversely, for IO-bound APIs it is considered useful (tm). So initialization will definitely remain async/promise based.
Perhaps it's common knowledge to JavaScript programmers but
asyncandawaitare not general purpose coroutines, that is to say, anasyncfunction does not necessarily suspend execution on eachawaitin the sense of unblocking the main event loop. This is because Promises run on the "microtask queue" and the browser will keep running them until there are no more left before it goes back to doing important things like responding to user input: https://developer.mozilla.org/en-US/docs/Web/API/HTML_DOM_API/Microtask_guide#microtasksObviously if you launch a bunch of async functions or Promises they will yield to each other but that is not actually what you want in most cases.
Concretely this means that using
asyncfor CPU-bound APIs is considered harmful (tm). So we have to removeasyncfrom most functions in the API.Conversely, for IO-bound APIs it is considered useful (tm). So initialization will definitely remain async/promise based.