Comment by jvanderbot
9 months ago
I know. But threading, and earlier processes, were less scalable but potentially faster ways of handling concurrent requests.
9 months ago
I know. But threading, and earlier processes, were less scalable but potentially faster ways of handling concurrent requests.
It's also much easier to reason about, since scheduling is no longer your problem and you can just write sequential code.
That's one way to see it. But the symmetric view is equally valid: async await is easier to reason about because you see were the block points are instead of having to guess which function is blocking or not.
In any case you aren't writing sequential code, it's still concurrent code, and there's a trade-off between the writing simplicity of writing it as if it was sequential code, and the reading simplicity of having things written down explicitly.
This “write-time vs read-time” trade of is everywhere in programming BTW, that's also the difference between error-as-return-values and exception, or between dynamic typing and static one for instance.