Hacker News new | ask | show | jobs
by SOLAR_FIELDS 1061 days ago
The inevitable question: what does Bun do that Deno doesn’t and vice versa? Competition is always good and I applaud it heavily. What is Bun’s killer feature over Deno and why would I pick Bun over Deno for a new project?
2 comments
spiffytech 1061 days ago
Personally, I like that Bun aims to be "Node, but better". That's all I ever wanted.

Deno's desire to rethink server-side JS adds friction in service of goals I don't value. They're gradually giving ground their aspirations (e.g., in my memory it was previously a point of pride to not interoperate with NPM), but it's still not a drop-in replacement and I don't think they want it to be.

Bun's goals align with mine, so it's the one I prefer using.

link
Jarred 1061 days ago
In a word: pragmatism. Bun is pragmatic where Deno is “by the book”. Node.js globals like process are Bun globals. You can use require() and import in the same file. Bun is faster, easier to use, and more compatible with the JavaScript ecosystem. There’s less new stuff to learn. And that also makes Bun easier to try in new and existing projects.
link