> blocking code is objectively easier to reason about than “jumping around” code.
This is precisely why await was introduced in the first place. Promise and callback code was impossible to reason about.
A Promise is not ordinary blocking code.
String res = someRestCall();
is.
I was agreeing with you. They introduced await because they know that
var s = await someCall();
someCall().then(…)
It’s a different question that async-await may have a few very specialist use-cases, that is not readily available in the preemptive model.