It's Not Just Node.js Anymore
summary
Non-browser runtimes multiply: Node, Deno/Dino, Bun, Cloudflare Workers and new entrants like WinterJS, each with different tradeoffs. WinterCG pushes shared APIs so code stays portable; example: a draft socket API exposing a global connect that is promise based, uses web streams and accepts only about four options versus Node TLS which exposes 49 TLS options. Cloudflare Workers ships a native implementation and a cross-runtime polyfill exists; Bun currently wins raw speed; migrate to ESM and prefer standards unless performance demands otherwise.
AI-written summary · about
chapters (14)
- 0:00Introduction
- 3:50Winter JS
- 11:16Opening a socket
- 13:51Window Navigator
- 15:36Runtime Specific APIs
- 18:24WinterCG
- 20:22Summary
- 23:04Questions
- 23:54Multiple run times
- 28:12Alternative run times
- 29:20Sanitization
- 31:21Picking a runtime
- 33:04The junior developers
- 33:52Zig vs Rust
related talks
25mNext-Gen Server JavaScript: Web Standards
23mDinos and Clouds: Node apps for Deno and Cloudflare Workers
07mBuilding a Node js runtime for the browser
26mTowards a stdlib for JavaScript Runtimes
46mState of Node.js 2025: While You Were Building Frontend...
19mDoes your NPM package run at Edge?
15mWrite once, run anywhere - cross-env JS
22mBun, Deno, Node.js? Recreating a JavaScript runtime from Scratch