On the map

At the centre Splitting functions into synchronous and asynchronous kinds forces that distinction into every piece of code a programmer afterwards writes. Holds BNBob Nystrom Read this korrent →

• Similar wording You cannot really understand the code you write unless you are also the one operating it. Holds CMCharity Majors
• Similar 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. Holds AHAnders Hejlsberg
• Similar 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. Holds CMCharity Majors
• Similar 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. Holds BNBob Nystrom
• Similar 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. Holds BNBob Nystrom
• Similar wording What trips up newcomers to Rust is not the code but the shape of their data. Holds ARAlice Ryhl
• Similar wording Object-oriented programming is how he sees the world, whatever the frontier says about functional programming. Holds DHDavid Heinemeier Hansson
• Similar wording Concurrency should stop being the programmer's problem and become the language designer's: it is better to impose vast pain on a few people than on a million. Holds TSTim Sweeney