Javascript Should Come With Batteries
summary
Claims that JavaScript runtimes should be batteries included and demonstrates a concrete stack: native TypeScript and JSX support, built-in testing linting formatting, web-standard APIs and permission prompts, a persistent KV key-value database with no setup, npm imports without node_modules and a single-binary install. Shows a deployed app with a visitor counter, a measured 13 second deploy, resumes persistent state after restart, and reports using about 16% of built-in tools — all without writing config files.
AI-written summary · about
chapters (14)
- 0:00Introduction
- 1:29JavaScript lacks standard lib
- 5:04Rust vs Go ecosystems
- 6:48Deno’s origin
- 7:31Deno’s built-in tools
- 9:38Secure permissions demo
- 11:22Web standards demo
- 13:09NPM and Express demo
- 15:25Linter and formatter demo
- 16:27Key-value DB demo
- 18:41Deno Deploy
- 20:29Global KV scaling
- 21:14Deploying demo
- 22:17Recap and call to action
related talks
38mJavaScript Should Come With Batteries
38mJavascript Considered...Useful
12mThe Goodness of JavaScript
38mBuilding Universal Apps
44mJavaScript in 2017: You might (not) need a framework
59mNo Strings Attached: JavaScript without Webpack, Transpilers, or Frameworks
30mTowards a simpler JavaScript ecosystem
41mJavaScript, Day 4001