I’m glad bun exists. I prefer deno’s logo, and am also glad deno exists. Neither of these products are things that I’m actively using, but if JS/TS etc were my preferred ecosystem, I think I’d be much happier with one of them than pure node at this point. Props for that.
In regards to this announcement, I’m slightly annoyed that they focused sooo much on these benchmarks, though, I guess I should have expected it; Bun has consistently been about SPEEEEEEEED.
In regards to this announcement, I’m slightly annoyed that they focused sooo much on these benchmarks, though, I guess I should have expected it; Bun has consistently been about SPEEEEEEEED.
Yeah, microbenchmarks like who can print “hello world” faster feels a bit disingenuous. As a mostly uninformed outsider, it actually makes me more skeptical, not less. That said, it might be more of a me thing than anything.
In regards to this announcement, I’m slightly annoyed that they focused sooo much on these benchmarks, though, I guess I should have expected it; Bun has consistently been about SPEEEEEEEED.
Yeah, I hope we see more real-world benchmarks after this 1.0.0 release.
But right now just by toying with Bun you can really feels that everything is snappy: creating a project, installing packages, running tests, etc…
I think I will do my own benchmarks at work as I consider switching parts of our stack from Python/Django backends to TypeScript and Bun makes it very appealing.
Oven will provide incredibly fast serverless hosting & continuous integration for backend & frontend JavaScript apps — and it will be powered by Bun.
…
The plan is to run our own servers on the edge in datacenters around the world. Oven will leverage end-to-end integration of the entire JavaScript stack (down to the hardware) to make new things possible.
As far as I can tell, Bun tooling is to Oven as Deno tooling is to Deno Deploy: a free platform that advertises a paid service.
Hmm. I think serverless in the heroku sense is great (you provide code, and they worry about deployment, logs, servers, backups, etc), but serverless in the lambda or cloudflare workers sense has been kind of a flop for everything but glue code and hacks.
Bun looks absolutely great, like cargo but for JavaScript. Congratulations on getting to 1.0 so fast, the progress has been amazing to see! Have been meaning to make a new personal website, and bun looks like a great option…
Congrats to the team on their launch! I find their batteries-included and It Just Works approach quite compelling.
I agree that the last few years have been rough for Node. JS (and TS) are everywhere and it’s made continual improvements, but the fractured ecosystem definitely makes revisiting and updating old projects tricky.
I’m glad bun exists. I prefer deno’s logo, and am also glad deno exists. Neither of these products are things that I’m actively using, but if JS/TS etc were my preferred ecosystem, I think I’d be much happier with one of them than pure node at this point. Props for that.
In regards to this announcement, I’m slightly annoyed that they focused sooo much on these benchmarks, though, I guess I should have expected it; Bun has consistently been about SPEEEEEEEED.
Yeah, microbenchmarks like who can print “hello world” faster feels a bit disingenuous. As a mostly uninformed outsider, it actually makes me more skeptical, not less. That said, it might be more of a me thing than anything.
Yeah, I hope we see more real-world benchmarks after this 1.0.0 release.
But right now just by toying with Bun you can really feels that everything is snappy: creating a project, installing packages, running tests, etc…
I think I will do my own benchmarks at work as I consider switching parts of our stack from Python/Django backends to TypeScript and Bun makes it very appealing.
What‘s their (planned) business model?
Per https://oven.sh/:
As far as I can tell, Bun tooling is to Oven as Deno tooling is to Deno Deploy: a free platform that advertises a paid service.
Hmm. I think serverless in the heroku sense is great (you provide code, and they worry about deployment, logs, servers, backups, etc), but serverless in the lambda or cloudflare workers sense has been kind of a flop for everything but glue code and hacks.
It shows an example of CommonJS & ESM in the same file. How does this work? Are they just compiling ESM to CommonJS & calling it a day?
From these docs (Low-level details section), it seems they do the opposite (cjs -> esm).
Link to release notes: https://bun.sh/blog/bun-v1.0
[Comment removed by author]
Bun looks absolutely great, like cargo but for JavaScript. Congratulations on getting to 1.0 so fast, the progress has been amazing to see! Have been meaning to make a new personal website, and bun looks like a great option…
Congrats to the team on their launch! I find their batteries-included and It Just Works approach quite compelling.
I agree that the last few years have been rough for Node. JS (and TS) are everywhere and it’s made continual improvements, but the fractured ecosystem definitely makes revisiting and updating old projects tricky.
I’m excited to see where they take this!