4 ms·

I’m not really sure that it is all that subjective — plain old serial, blocking code is objectively easier to reason about than “jumping around” code. It’s a d

by kaba0 3y ago

I’m not really sure that it is all that subjective — plain old serial, blocking code is objectively easier to reason about than “jumping around” code. 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.

vips7L 3y ago
> 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.
- kaba0 3y ago
  A Promise is not ordinary blocking code. String res = someRestCall(); is.
  - vips7L 3y ago
    I was agreeing with you. They introduced await because they know that var s = await someCall(); is way easier to reason about than: someCall().then(…)
    - kaba0 3y ago
      Oh, I see! Sorry for the misunderstanding!