JavaScript Should Come With Batteries
summary
Argues that JavaScript needs batteries included and shows a runtime that delivers: a single-binary runtime with built-in TypeScript, browser-standard fetch/streams and CompressionStream, a permissions-by-default model that prompts for file/network access, integrated lint/format/test tooling with zero config, and a built-in Deno KV persisted locally (SQLite) and deployed cloud-backed (FoundationDB). Demonstrates importing npm and URL modules, running Express, compressing streams, and deploying to Deno Deploy in 9s; claims 250,000 monthly users and says the demo covers ~16% of available tools.
AI-written summary · about
chapters (26)
- 0:00JavaScript lacks batteries
- 4:45Rust and Go tooling
- 6:52Deno as solution
- 8:53Live Deno demo
- 10:19Deno IO and permissions
- 12:43Web APIs in Deno
- 15:53JS from URLs in Deno
- 17:19Import npm packages
- 19:26Express server with Deno
- 21:15Linting and formatting
- 22:19Deno KV storage
- 24:26Deno open-source model
- 25:09Deploy to Deno Deploy
- 27:21Recap Deno’s approach
- 28:25Batteries boost productivity
- 29:31Edge computing with Deno
- 30:57Q&A: Why Deno?
- 31:19Q&A: Top-level await
- 31:40Q&A: Hosting Deno
- 32:21Q&A: Linting rules
- 33:27Q&A: TypeScript updates
- 34:32Q&A: Web standards
- 35:37Q&A: Reset Deno KV
- 36:19Advice for juniors
- 37:43Q&A: Open-source benefits
- 38:04Closing remarks
related talks
24mJavascript Should Come With Batteries
30mDeno is a New Way to JavaScript
56mDeno, a new way to JavaScript
24m[Eng Sub]Deno: Next Generation JavaScript Runtime
34mTowards a simpler JavaScript ecosystem
38mJavascript Considered...Useful
31mDeno: The JavaScript Runtime for the Serverless Era
12mThe Goodness of JavaScript