Hacker News Reader

Comment by rr888 | Hacker News Reader

What was the other node alternative that was faster? I was going to try it out, but can't remember it. Deno seems too much of a change.

View on HN

I think you mean Bun https://bun.sh

Please share any feedback jarred@oven.sh

Bun?[1]

Which is a bigger change then Deno, as that is basically node with some more stuff included (same engine, lead developer, similar attitude towards standard library etc.), whereas Bun is using the JavaScript Core engine from Safari.

[1]: https://bun.sh

Sorry, but this is nearly the exact opposite of the truth. The choice of underlying JS runtime only really affects performance. Bun is specifically designed to be fully Node-compatible (including the standard library, etc), while Deno is specifically designed to be a break that leaves Node's baggage behind (the current post is one of the pragmatic compromises they've made on that intent, but the intent is still there). Both runtimes add their own stuff on top of the above, but Bun is definitely the most "like Node" in terms of compatibility/familiarity/ease of adoption (and I say this as someone who prefers Deno).

Do you mean bun??

There's still a whole lot of confusion around which is actually faster. Both have published counter benchmarks to prove that they are faster than their rival.

In my experience, v8 has a better memory and garbage collection system, but JSC produces faster code. I don't know how that works in a server context though.