Splitting functions into synchronous and asynchronous kinds forces that distinction into every piece of code a programmer afterwards writes.

Added to korrents 1 Feb 2015 · How quotes work · Something wrong? Tell us

Related korrents

Our reading — they may agree, disagree or merely touch the same thing. Closest first: a shared subject counts for most, then how near the wording is.

• You cannot really understand the code you write unless you are also the one operating it. CMCharity Majors12 Aug 2026similar wording
• Function colouring is the real cost of async/await, and green threads like Go's avoid it — but for an existing runtime such as JavaScript or C#, async/await was still the right solution. AHAnders Hejlsberg13 May 2026similar wording
• You can now generate ten thousand variants of a function faster than you could write it once, and that economics pushes software towards replacement rather than repair. CMCharity Majors12 Aug 2026similar wording
• Asynchrony should be a property of how a program is run, not a colour baked into the type of every function in the standard library. BNBob Nystrom1 Feb 2015similar wording
• Async/await makes asynchronous code easier to write without healing the split it created, and the divide reappears as soon as you write a higher-order function. BNBob Nystrom1 Feb 2015similar wording

See this on the map →