Supper Club × Ryan Dahl and Deno

Episode Summary

Executive Summary: Ryan Dahl explains why JavaScript remains the web’s durable default, and how Deno aims to modernize server-side JS with Rust, TypeScript, stronger security, and web-standard APIs. The episode covers Deno’s goals, NPM compatibility, Fresh, edge/serverless deployment, and the broader shift toward browser-compatible, high-level development on the server.

Main Topics: Why JavaScript remains the default web language: Ryan argues JavaScript persists because the web is the medium of communication and its core technologies—HTTP, CSS, HTML, and JavaScript—will remain central for years. Why Deno was created: Deno was built as a response to Node’s slow evolution, the rise of ECMAScript modules and TypeScript, and the need for better security and a more modern runtime architecture. TypeScript as JavaScript 2.0: The discussion frames TypeScript as a restrained, practical extension of JavaScript that will likely influence future browser support via type-stripping and comments-based proposals. Deno’s runtime design and performance: Deno is written mostly in Rust, uses V8 plus an async runtime, and aims to outperform Node through better event-loop design and tighter native bindings. NPM compatibility and web-standards direction: Deno is adding stable NPM support to ease adoption, while still encouraging browser-compatible, WinterCG-aligned APIs and fewer Node-specific legacy patterns. Fresh and server-side rendering at the edge: Fresh demonstrates Deno’s philosophy: minimal tooling, just-in-time builds, SSR-first design, and fast deployments through Deno Deploy and edge-style infrastructure. Developer tooling and batteries-included workflow: Deno includes format, lint, and test tools by default to reduce decision fatigue and standardize workflows, contrasting with Node’s more fragmented ecosystem.

Key Arguments: JavaScript will remain relevant because the web itself is not going away, making JS a future-proof investment for developers. Deno was created because Node’s architecture and governance made it hard to rapidly adopt modern JavaScript features and security practices. TypeScript is likely the practical model for JavaScript’s future because it adds types without abandoning the JavaScript ecosystem. Browser-compatible APIs and WinterCG-style server APIs are the better long-term direction than Node-specific abstractions. NPM support is necessary for adoption, but Deno still wants developers to write against web standards rather than legacy Node APIs. A batteries-included runtime reduces tooling confusion and improves developer experience by standardizing formatting, linting, and testing. Server-side rendering and edge deployment are increasingly the best defaults because they improve performance, latency, and deployment speed.

Data Points: Deno Open Source Age: 4 years - Ryan says the open source Deno project has been worked on for four years. Deno Compatibility Layer: 80% to 90% of NPM packages - Ryan estimates most NPM packages work out of the box with Deno’s new support. Deno Deploy cold start: under 100 milliseconds - Ryan describes Deno Deploy as having very fast cold starts. TypeScript proposal stage: stage one - Ryan mentions TC39 proposals for types as comments are currently only stage one. Type stripping speed: essentially zero time - Ryan says Deno strips types very quickly before handing raw JavaScript to V8. Fresh deploy availability: about 5 seconds - Ryan claims Fresh/Deploy can make a PR available in roughly five seconds. Lighthouse score mentioned for website: 55 - Wes and Ryan discuss Wes’s site score during the server-rendering conversation. First contentful paint mentioned: 1.1 second - Ryan references a Lighthouse run for Wes’s site. TypeScript compiler implementation: Microsoft's TSC - Ryan says Deno uses Microsoft’s TypeScript compiler for type checking. Rust project size: over 500 crates - Ryan describes Deno as one of the largest Rust projects.

Pivotal Quotes: "JavaScript has become the default programming language." — Ryan Dahl: Ryan explains why JavaScript remains central despite its imperfections. "Our main goal with Deno is to make it the easiest, the fastest, and the most secure server-side JavaScript runtime." — Ryan Dahl: Ryan summarizes Deno’s core product mission. "As much as possible, we should be running this on the server." — Ryan Dahl: Ryan argues for server-side rendering and edge-first execution for web apps.

Implications: The web stack is moving toward standardized, server-side, edge-executed JavaScript with stronger defaults. Developers should expect more browser-compatible APIs, less Node-specific code, and faster, simpler toolchains.