korrents

korrents · piece

What Color is Your Function?

Bob Nystrom · 1 Feb 2015 · journal.stuffwithstuff.com ↗

3 korrents from this piece

Bob Nystrom did not write this page.

Every claim below was made in this piece, quoted word for word and numbered in the order the piece makes them, so you can read it there rather than take our word for it. The sentence above each quote is our reading of the claim, not their wording. Each quote was checked against a stored copy of the page at build time; where the two differ, the quote is the fact.

  1. Our reading

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

    Their wordsNo matter what, you'll have to think about color constantly.
    Interesting

  2. Our reading

    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.

    Their wordsIt is better. I will take async-await over bare callbacks or futures any day of the week. But we're lying to ourselves if we think all of our troubles are gone.
    Interesting

  3. Our reading

    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.

    Their wordsConcurrency in Go is a facet of how you choose to model your program, and not a color seared into each function in the standard library.
    Interesting