Advertisement
Advertisement
⚡ Community Insights
Discussion Sentiment
63% Positive
Analyzed from 2114 words in the discussion.
Trending Topics
#bun#code#rust#node#https#rewrite#release#dead#com#argument
Discussion Sentiment
Analyzed from 2114 words in the discussion.
Trending Topics
Discussion (70 Comments)Read Original on HackerNews
- I have a couple of projects that handle images. I was including Sharp, but since these are side projects in a small VM, often a redeploy that recompiled Sharp just crashed the full VM (out of memory). Bun includes Bun.Image[1] natively, which is built around Sharp's API, so swapping Sharp out was very easy, and now deploys are a breeze (and swapping it in would be just as easy).
- Bun's JSX support is a godsend. I've replaced almost all my side projects that were backend rendered from Pug, Handlebars, and other various templates I used to have to just pure JSX. Heck, this made it trivial to make a side projects where the Favicon was a dynamic SVG [2]
[1] https://bun.com/docs/runtime/image
[2] https://stocksreader.com/portfolio?%5Egspc=10&amzn=10&msft=1...
Have you tried 1.4?
Idk why people have become so invested in this.
> Unused code is one issue. A project called Buz[1] found over 11,000 lines of dead code from the Rust port. [1]: https://github.com/jazzzooo/buz
When in fact Buz is a fork of the pre-Rust Zig version of Bun.
The OP has no credibility.
People _really_ want there to be success stories for llms and they will go through all lengths to discredit and disparage folks questioning the space.
Apart from pro-AI or anti-AI posturing how have the last few months not looked good for Bun, exactly? I use it daily and I've seen basically zero regressions. I get it, you don't like AI or you like Zig over Rust, or whatever. I just haven't seen any serious argument that Bun has somehow become worse software.
> The project has over 5k open pull requests, which is the largest number of pull requests I’ve seen.
Terrible argument, and not really an argument at all.
> The biggest worry is, of course, the code itself.
I agree, so look at the code and point out what's wrong with it.
Insofar as Andrew Kelley is concerned, it's obvious he has an axe to grind and is salty about Bun embarassing Zig (which he freely admits). Not sure why you'd invoke an unreliable narrator as some sort of final nail in the coffin.
The blog post states quite clearly that Bun stopped posting any release.
During the Zig/pre-Rust days, Bun was posting s new release each 2-3 weeks.
Since then, Bun's Rust migration is correlated with a complete stop of Bun's release cadence.
[1]: https://github.com/jazzzooo/buz
A bizarre accusation. It's a fork of Bun that says they removed the dead code. All you have to do to see the diffs is look at its history. Most of the commits are code removal.
It's a fork of Zig bun, though, not Rust, so hardly relevant to the AI argument.
> Buz is an early-stage experimental fork of pre-Rust Bun.... Over 11,000 lines of dead code removed from upstream Bun.
The article answers this. hint: they're not shipping.
> I get it, you don't like AI or you like Zig over Rust, or whatever
The article doesn't argue for either of these. hint: it's arguing that the team is not shipping.
> Terrible argument, and not really an argument at all.
It's an argument for the devs not shipping
> I agree, so look at the code and point out what's wrong with it.
It's not being shipped.
Hope that helps.
They're shipping though.
Claude Code and many others use it. There's just not been a "public" release.
The bun rewrite is looked to as proof that this sort of full-throttle vibecoding is the future of software development, at least for large porting projects like this one, and for many people on this site that is a high stakes question.
To prove that, a proper release is needed, and the Bun community needs to adopt it. There's a huge partisan eagerness to declare the Claude Code release or anecdotal experiences on the canary as victory, but the viability of 1.4 hasn't been demonstrated until it has been released and adopted by the bulk of the community.
There isn't actually any hurry on that. Nobody needs Bun 1.4 tomorrow. It's Jarred that keeps saying it'll be released tomorrow, while the code churns at an astonishing rate (see below). People with a skeptical outlook will inevitably suspect that he doesn't have confidence in the release and is struggling to acquire it.
Github insights for the last week:
> Excluding merges, 57 authors have pushed 349 commits to main and 6892 commits to all branches.
> On main, 2026 files have changed and there have been 189,502 additions and 133,836 deletions
What are you talking about? I'm running 1.4 canary (the Rust rewrite) right now.
Hope that helps.I think GP was pointing out how bun's release cadence stalled and the project is going nowhere at the moment.
https://github.com/oven-sh/bun/releases
The project was pretty healthy up to 1.13.14, but since may they stopped shipping anything.
That's quite odd for a project that just went through a major rewrite and is lauded as being developed primarily by LLM coding assistants.
Personally I expected the release cadence was going to go through the roof, but instead it flat lined.
I suppose it’s one thing to rewrite code and make tests pass. But a lot of my own CPU cycles when coding go to making the code understandable, modular, editable etc. IME Claude is not great on these.
Maybe it doesn’t matter? Maybe the spaghetti makes sense to Claude, and when you say “hey add this feature”, no problem?
But maybe it will turn into a worse ball of spaghetti, with no nicely curated tests, hacks on hacks on hacks and never ending loops of whackamole of “just change this one line and rerun tests”.
I can imagine both - let’s see.
edit: There's also nub which is built on top of Node.js and removes some rough/legacy edges: https://github.com/nubjs/nub
https://github.com/nodejs/node/issues/63096
https://fetchable.org/
They do seem to have just merged in support for Web Workers though, which I've been following for a while: https://github.com/nodejs/node/issues/43583
So I don't think they're opposed to standardising, but it's trickier when you have some past cruft built up. Lets not forget that the fetch() standard was built for browsers, and is a bit of a stretch to make it work on servers at all. You have to diverge from the fetch spec to even make it make sense in a server environment (with things like Cookies handling off the top of my head).
- esbuild - this is normally for TS compilation, which Node can run natively now by stripping types: https://nodejs.org/docs/latest/api/typescript.html#type-stri...
- jest/vitest: Node has a test runner: https://nodejs.org/docs/latest/api/test.html
- dotenv: Node can read .env files: https://nodejs.org/docs/latest/api/cli.html#--env-filefile
Performance, maybe you're right - but if you're doing any IO, I doubt the runtime is really the bottleneck.
You need a "separate" tool called npm to install packages. It's dead slow so they added corepack. Another extra tool. Then you use it to install yarn or pnpm. Another extra tool. It might still be slower than bun...
In the past you need to transpile typescript with other tools. It can only run js out of the box. The later fix was a wasm build, which means slower than it could be. Another 1/2 job.
Many more examples in many areas but anything Node tries to do itself feels 1/2 baked.
Bun and Deno are faster than Node because it is a 1/2 job at its core. It has v8. It has the tools. It could be done but no. It did nothing for years until Deno and Bun came on the scene to nudge it.
This is.. clickbait ?
They were pleased to be faster than Go in the "Hello World" benchmark, but unfortunately, they lag behind Node.js and Deno in complex real-world workloads.
I would love to know how much token they spent on the rewrite starting from deciding to rewrite till they actually ship. I assume since the beginning of this whole rewrite saga they have been spending tokens on it every day so the number that Jarred mentioned in his blog post has increased a lot since then.
Also assuming the future releases will be done through AI as well I wonder how much it will cost for each of them.
> Our conclusion is deliberately modest: under the conditions Prisma Compute cares about, the Rust rewrite behaved better than the stable release we had been testing. That was enough to change what we shipped.
https://www.prisma.io/blog/bun-rust-rewrite-prisma-compute
need 5 trillion more Opus token
Your whole scientific endeavor in this seemed to thrive on the rock solid foundation of tweets.
And all those referencing of the Kelly post makes this even more of a clickbait. All you had was to put all the ingredients of a post that will draw the crowd but offer very little on the subject matter it purported to discuss
The article lists various promised release dates, are they incorrect?