Bun 1.1

Original Article ↗ Hacker News Discussion ↗

Overall reception & performance

  • Many commenters are impressed by Bun’s speed (package installs, test runner, bun upgrade, TS execution).
  • Some real-world reports: large TS monorepos and test suites run much faster than with Node + Jest; ts-node comparisons show big startup gains.
  • Others note frequent segfaults or runtime/tooling crashes in earlier attempts, saying it still feels “not quite baked.”

Integrated tooling & TypeScript

  • Strong appreciation for the “one tool” model: runtime, package manager, bundler, test runner, TS runner, web server, shell, and single-file binaries in one install.
  • Developers like dropping stacks of separate tools (node, npm/yarn/pnpm, ts-node/tsx, jest, nodemon, esbuild, etc.).
  • Bun transpiles TS to JS without type checking; people still run tsc --noEmit separately or rely on IDEs, and some wish Bun had integrated type checking.

Compatibility & missing features

  • Good Node/npm compatibility reported for many projects; some say Bun was a drop-in dev replacement while still running Node in production.
  • Others hit incompatibilities (e.g., Prisma, Remix/Vite, uncaught exception handling, sourcemaps with bun build, missing dgram, no Next.js support yet).
  • Worker API, UDP/dgram, and better Jest compatibility are recurring asks.

Telemetry & privacy

  • Telemetry is enabled by default but reportedly not currently sent anywhere; it’s mainly used for crash messages.
  • Users find documentation of telemetry and opt-out (e.g., DO_NOT_TRACK=1) too hidden; strong sentiment that it should be opt-in or at least clearly presented during install.
  • Old machine-id related code is called out; maintainers say it’s dead code but concern remains until fully clarified with a formal privacy policy.

Windows support & implementation details

  • Windows support in 1.1 is widely praised; Bun passes ~98% of its own cross-platform test suite, with remaining failures described as platform-specific.
  • Some critique the checked-in Windows shim binary and use of undocumented NT APIs, worrying about maintainability and security; others justify NTDLL usage for performance but the benefit here is disputed.

Ecosystem position, governance & business model

  • Many like Bun as a faster, more ergonomic Node alternative; others prefer Node’s maturity and boring stability, especially in large organizations.
  • Comparisons with Deno: Bun seen as more aggressively Node-compatible; Deno praised for fine-grained permissions and URL-based modules.
  • Some ask for clear support/EOL and stability policies (similar to Node/Python) and question long-term viability and VC funding; others note MIT licensing and possibility of forks.
  • Community tooling choice (Discord vs FOSS platforms) triggers debate but no concrete change; Bun team says they’d switch if a better open-source alternative actually wins adoption.

Other features & wishlist

  • Interest in Bun shell (tagged template-based, safer shell scripting), macros, FFI, and single-binary builds; cross-compilation and smaller binaries are requested.
  • Questions remain about hosting/“edge” story and potential paid worker-style offerings.