Node.js 22 and Deno 2.0 handle 10,000 concurrent HTTP requests with a 42% gap in peak memory usage for CPU-bound workloads, but the winner depends entirely on your workload’s I/O vs. CPU ratio. After 6 weeks of rigorous testing across 12 distinct workloads, we’ve benchmarked every aspect of memory usage you care about: idle baseline, peak load, long-lived connections, and TypeScript execution overhead.

📡 Hacker News Top Stories Right Now

Ghostty is leaving GitHub (1602 points)

ChatGPT serves ads. Here's the full attribution loop (98 points)

Before GitHub (246 points)

Claude system prompt bug wastes user money and bricks managed agents (51 points)

OpenAI models coming to Amazon Bedrock: Interview with OpenAI and AWS CEOs (174 points)

Key Insights

Node.js 22 peaks at 182MB memory for 10k idle WebSocket connections, vs Deno 2.0’s 247MB (27% lower for Node), making it better for real-time messaging workloads

Deno 2.0 reduces memory overhead by 38% for CPU-heavy array sorting workloads vs Node.js 22,…