If you wind up writing the word "await" in your codebase more than once, you're doing it wrong. You will quickly see how futures/promises wind up taking over all of your code. This is a very good thing. You shouldn't need to block, ever.
Sincerely,
Scala coders
It makes code more readable and easier to write, but doesn't fundamentally change how it is working under the hood, as far as I am aware.
var txt = await read();
// This code is blocked until read() completes.
console.log(txt); read((err, txt) => {
console.log(txt)
})
read().then((txt) => console.log(txt))
async function is blocked on await statement, after all that's why it has such a name.
It does not block the whole VM but task (async function) is effectively blocked for an observer inside it.
http://docs.scala-lang.org/overviews/core/futures.html#block...
Also, how is Scala doing it?
Why have you decided to rewrite everything?
Sincerely, Everyone else. (Obviously not JavaScript coders, sadly...)
P.s. I can only hope you have a somewhat sane release story now.