Comment by groundzeros2015 10 days ago I agree. I don’t think callbacks are an underbaked language feature. 2 comments groundzeros2015 Reply t-writescode 10 days ago In another part of the thread, you lament the use of callbacks. May I ask you what you think async/await is, except syntactic sugar that wraps around the callback pattern? groundzeros2015 9 days ago Certain architectures focused around callbacks have problems. But their existence is not a burden on the language design.Node.js has a problem where every standard library function has a callback and blocking version. At least they just committed to doing both.
t-writescode 10 days ago In another part of the thread, you lament the use of callbacks. May I ask you what you think async/await is, except syntactic sugar that wraps around the callback pattern? groundzeros2015 9 days ago Certain architectures focused around callbacks have problems. But their existence is not a burden on the language design.Node.js has a problem where every standard library function has a callback and blocking version. At least they just committed to doing both.
groundzeros2015 9 days ago Certain architectures focused around callbacks have problems. But their existence is not a burden on the language design.Node.js has a problem where every standard library function has a callback and blocking version. At least they just committed to doing both.
In another part of the thread, you lament the use of callbacks. May I ask you what you think async/await is, except syntactic sugar that wraps around the callback pattern?
Certain architectures focused around callbacks have problems. But their existence is not a burden on the language design.
Node.js has a problem where every standard library function has a callback and blocking version. At least they just committed to doing both.