korrents

Bob Nystrom

@bob-nystrom · 3 positions · 0 changes of mind

Programming language engineer on the Dart team at Google and author of Game Programming Patterns and Crafting Interpreters. He writes about language design at journal.stuffwithstuff.com.

Everything they publish, on ppll ↗

Bob Nystrom did not write this page.

We collected these quotes from things they published elsewhere, and every quote links to where it was said. They have no account here and have not endorsed this site. Quotes are word for word; the short line under each one is our own restatement, not their wording. Their own site. Is this you? Claim it or ask us to remove it. Or tell us what is wrong here.

  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.

    ↗What Color is Your Function?journal.stuffwithstuff.com 1st of 3 in this piece

    Interesting

  3. 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.

    ↗What Color is Your Function?journal.stuffwithstuff.com 2nd of 3 in this piece

    Interesting

  5. 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.

    ↗What Color is Your Function?journal.stuffwithstuff.com 3rd of 3 in this piece

    Interesting