Yesterday, version 1.0 of Bun was officially unveiled, and now it's here, ready for use.
This marks a significant milestone in the JavaScript/Type...
For further actions, you may consider blocking this person and/or reporting abuse
Speed is noticeable. Just Bun needs some stabilisation.
I totally agree.
I also wonder, if they can keep their current development speed.
I'd rather focus on quality, but that's personal opinion.
Interesting possibilities is the import rust file to the js project.
Wasn't Bun the thing that the CEO/owner/whatever said they wanted everyone involved to basically give up their lives to dedicate themselves to the project?
just a matter of time bun will be implemented for those who want boost performance
TechEmpower's last year benchmarks don't feature Bun. Do you have another set of benchmarks lying around? I am interested in staying informed with real numbers. You see, people always praise Node for its "high performance" and this is clearly a lie. Let's not fall into the same mistake with Bun.
There is this bun-http-framework-benchmark that is regularly updated and has comparison with a few libs like express, elysia (express like for Bun). Take a look at the benchmark but probably take it with a grain of salt.
This other article Node.js vs. Deno vs. Bun: JavaScript runtime comparison might be interesting as well
Thanks!
Most of the benchmarks are missing the comparison of RAM and CPU consumption, which is imo very important.
More important in real world, than raw throughput.
Well, there are a lot of benchmarks currently available. And if you look into a benchmark from last year, you probably won’t find Bun, as it is too young.
Also, as I said, I’m not so much into the request/sec thing, as in real world, you most of the time do stuff like database queries which “drop” that rate.
If you have 1mio req/s on a single instance, you might think about what’s maybe wrong on your infrastructure. Fault tolerance, DoS protection and so on?
What I can say: for example running unit tests is outperforming any other comparable node setup. Feels like the console output is the bottleneck here 😂.
Also, the startup/reload times are impressive compared to any other solution I tried for typescript.
You simply work faster.
And that’s mostly because Bun calls a way more often native functions compared to node.
Great overview of Bun 1.0! 🎉 Bun truly raises the bar with its all-in-one approach, covering runtime, package management, and bundling in one swift toolkit. Beyond speed, which is impressive on its own, Bun's Node compatibility stands out—it’s a “drop-in” replacement that lets you run many Node APIs, minimizing the learning curve for anyone familiar with Node.js.
And while speed in HTTP handling is often highlighted, Bun’s efficiency goes deeper: fast TypeScript support, ESM & CommonJS module compatibility, and even built-in testing mean less dependency on extra tooling. For developers working on IoT or edge functions, Bun's lower memory usage and native support for Web APIs like
fetchmake it a perfect fit.We also explored how Bun compares in real-world use cases against Node and Deno, diving into where it can be a game-changer. If you're curious, check it out here: scalablepath.com/nodejs/bun-node-a...
One thing I miss in most articles about bun, that in fact the speed of bun only came from time savings on start and not from a faster execution. Many people will be misled by the statement that bun is fast, if you compare both with a long time running application, you will see that v8 can be faster than JavaScriptCore. So yes, bun is really fast on the edge, but Node.js points for long time running applications.
Impressive