I am worried about Bun

Original Article ↗ Hacker News Discussion ↗

Concerns are mounting around the future of the Bun JavaScript runtime after its acquisition by Anthropic, whose rapidly evolving Claude Code product is widely perceived to be degrading in quality and usability. Commenters worry that the same growth pressures, AI-driven “vibe coding,” and unclear monetization that plague Claude Code could eventually undermine Bun’s reliability, even as its maintainers point to active development and technical improvements. Many developers say they still like Bun’s performance and “batteries included” design, but are reevaluating their dependence on it and considering more conservative options like Node.js, Deno, or pnpm for long-term stability.

Concerns about Bun’s Future Under Anthropic

  • Many worry that Anthropic’s acquisition will eventually push Bun in the same direction as Claude Code: more constraints, opaque behavior changes, and “business over developer” priorities.
  • Others argue Bun is an internal tool for Anthropic, not a consumer product, so incentives align with keeping it stable and performant rather than monetizing it directly.
  • Some see this as part of a wider pattern where acquisitions gradually import the parent company’s culture and “shitty practices,” though a few note there are counterexamples and say it’s too early to judge.

Current Technical State & Reliability of Bun

  • Several users report great DX: single-binary deploys, built-in SQLite, test runner, TS/JSX support, bun.$ for shell, fast watch mode, and fewer dependencies.
  • Others report severe production issues: memory leaks, CPU runaway, API incompatibilities, brittle patch releases, and bugs around installs and postinstall scripts. Many say they reverted to Node for production.
  • A Bun maintainer states stability has improved post‑acquisition, development pace is higher, and lists upcoming features (smaller binaries, HTTP/3 support, image processing, better process control, SSL optimizations).

AI “Vibe Coding” and Code Quality

  • Multiple comments criticize heavy use of LLMs in Bun and in Anthropic tooling: large AI-generated PRs, AI-written docs described as “slop,” and fear of a fully vibe‑coded codebase.
  • A former Bun engineer reportedly complained about excessive AI use and unreliable AI-generated changes.
  • Others counter that AI-assisted development is fine if results compile and pass tests, but worry about long‑term maintainability and subtle bugs.

Alternatives and Migration

  • Some switch or plan to switch from Bun to Node + pnpm, citing Node’s new TS support, built‑in SQLite/testing, and more predictable governance (OpenJS Foundation).
  • Deno is repeatedly suggested as a mature Node alternative with strong security model and JSR ecosystem; others mention tools like vite+, PerryTS, aube, and traditional Node as safer bets.
  • Several argue Bun is easy to replace today, so risk is acceptable; others prefer to avoid deep lock‑in now to prevent future migration pain.

Funding, Enshittification, and OSS Sustainability

  • Thread repeatedly questions VC‑funded runtimes (Bun, Deno) and AI labs’ unsustainable economics.
  • Some see Claude Code’s limits and third‑party harness crackdowns as early “enshittification”; others insist these are capacity and cost‑control reactions, not the classic ad‑driven pattern.
  • Broader concern: infrastructure projects rely on unstable funding (VCs, acquihires) because the industry lacks good models to pay for critical OSS.