Friendship ended with Deno, now Node is my best friend

234 points · 150 comments on HN · read original →

Points and comments are a snapshot, not live.

The author switched back to Node after years with Deno, citing Node's modernization and Deno's decline.

Node v26.10.0 now supports TypeScript (though refuses to strip types in node_modules), modern ECMAScript features, and improved APIs like node:fs. The author migrated a static site generator from Deno to Node with minimal changes and saw 15% faster builds. Package management uses PNPM with minimumReleaseAge:1440 to delay malware. Deno is criticized for broken ZSH integration, JSR 429 errors, concurrent HTTP bugs, layoffs, and a shift to AI-focused products. The author removed Deno via brew.

What commenters are saying

Commenters are split: some praise Bun as lighter and faster than Node or Deno, citing zero-dependency apps and riscv64 support. Others defend Node as a safe, boring, long-lived choice. A Bun critic notes its GET implementation rejects request bodies, breaking compatibility with tools like Elasticsearch and Axios. One commenter laments Deno's decline after layoffs and no roadmap. Another jokes that software makes better friends than people.