korrents
Kenton Varda

What Kenton Varda thinks about JavaScript

@kenton-varda · 26 positions · 0 changes of mind

Engineer at Cloudflare who designed Workers, Durable Objects and Cap’n Proto; earlier the primary author of Protocol Buffers v2 at Google, and co-founder of Sandstorm.io.

Everything they publish, on ppll ↗ Who they are, on wiqqi ↗

Kenton Varda 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.

2 dated positions, 2021 to 2024, in their own words. Our reading of what Kenton Varda has said — not written or endorsed by them.

2 positions so far — this page is not yet offered to search engines.

  1. Our readingSynchronous database queries help avoid subtle bugs, because every await is a chance for the state of the world to change underneath the code.

    Their wordsMore importantly, though, synchronous queries help you avoid subtle bugs. Any time your application awaits a promise, it's possible that some other code executes while you wait. The state of the world may have changed by the time your await completes.

    ↗Zero-latency SQLite storage in every Durable Objectblog.cloudflare.com

  2. 3 years earlier

  3. Our readingOn a serverless platform, a runtime upgrade must never break a live application, because developers have no control over when upgrades happen.

    Their wordsIn the old world, if the Node.js maintainers decide to make a breaking change to an obscure API between releases, it's OK. Downstream developers are expected to test their code before upgrading, and address any breakages. But in the serverless world, it's not OK: developers have no control over when upgrades happen, therefore upgrades must never break anything.

    ↗Backwards-compatibility in Cloudflare Workersblog.cloudflare.com