Live data from Hacker News

How is the Bun rewrite in Rust going?

lockwood.dev

341–350 of 412 posts

Re: How is the Bun rewrite in Rust going?

#341

Earlier quoted context omitted.

I don't see how it does. Claude Code is an extremely widely used product; the preceding comment offered an objective evaluation target, not a "trust me it's good" argument.

I don't see how Claude code being a widely used product is relevant to the person who orchestrated the Rust rewrite of bun saying that the orchestration of the Rust rewrite of bun went well. Wc eend is a widely used product as well, if that helps. Ah, for context, which I suspect you may be unaware of, Jarred (the person who said the rewrite to rust went well) is the creator of bun, and the guy behind the rewrite.

I think the chain of reasoning is not hard to follow:

1. Assume the Rust rewrite of Bun went badly

2. Then something must be grievously wrong with a released bun runtime based on that code

3. Claude Code uses the released bun runtime based on that code

4. From #2 and #3, something must be grievously wrong with Claude Code

5. If something were grievously wrong with Claude Code, users would reduce use of Claude Code and use alternative tools

6. From #4 and #5, users are reducing use of Claude Code and using alternative tools

7. Claude Code has wide use and use is growing across all software engineering verticals

8. #6 and #7 contradict

9. From the contradiction, the assumption in #1 is false

The parts that are not explicitly spelled out here are an exercise for the reader. It doesn't really matter if the guy who wrote Bun said this or my uncle said this.

Re: How is the Bun rewrite in Rust going?

#342
post #179

Earlier quoted context omitted.

Take as long as you need to ensure software quality. A month without a release isn't a big deal and whomever needs a specific feature can offer to contribute or build themselves. Node has 4-6 weeks without a meaningful release (other than security stuff) pretty much every December. I think the criticism in the article is unfounded and whomever needed/wanted a release should have asked first instead of writing an "ang…

What is Node getting every 4-6 weeks that makes it noteworthy when it doesn't?

Text imports (experimental), native addon ESM support, blob textStream(), ReadableStreamTee, byob for readFile, better event loop monitoring and lots of security fixes as well as more minor bug fixes and improvements. (Last 4-6 weeks)

Re: How is the Bun rewrite in Rust going?

#343
post #179

Earlier quoted context omitted.

Take as long as you need to ensure software quality. A month without a release isn't a big deal and whomever needs a specific feature can offer to contribute or build themselves. Node has 4-6 weeks without a meaningful release (other than security stuff) pretty much every December. I think the criticism in the article is unfounded and whomever needed/wanted a release should have asked first instead of writing an "ang…

Author here: I don't need or want another Bun release or an NPM release or anything like that. Like I very clearly say in the article I just got chatting with a peer about the Bun rewrite and I decided to take a look. I'm consistently skeptical about new tech whether it is NoSQL or Blockchain or Serverless. Some of the things I'm skeptical about fail and some succeed.

The bun Port is a phenomenal engineering achievement that would have taken a team of people over a year or two to deliver previously - look at the TypeScript port for example (and they had llms).

The fact it's taking a while to release is still insanely fast. I'm sure they may be some bumps.

Being skeptical is good and some stuff succeeds and some doesn't - but building tools is still fun and cool, whether it's useful or widely adopted or not :)

Re: How is the Bun rewrite in Rust going?

#344
post #204

Earlier quoted context omitted.

Why are you resistant to adding a sentence to the article that notes that Claude Code uses the rewrite? Do you think it would weaken the article? When I said it would improve the credibility I did mean it. My instinct on reading the article this morning was "this person doesn't know that Claude Code runs on Bun, which weakens their credibility in presenting the argument they are making here."

To me this seems like an odd preoccupation for an article that is very little about the Bun rewrite as a running program and very much about the process of the re-write and how it came to be in commits to the repository. You could argue that the release tag isn't important - but at the top of this comment thread a member of the team confirms they delayed the release to finish some extra testing. So the ambiguity arou…

Author here: Exactly.

I had a funny thought that Bun might add a release tag while I was still writing the article. In that case I'd still publish it, because the point is we still don't know the cost it took to get to a viable, wide, release. The $165k isn't the full story.

Re: How is the Bun rewrite in Rust going?

#345
post #290

I don't quite understand the focus on the token cost of this rewrite. Obviously, we should examine if this rewrite is good, effective, good for the product etc., but the token cost seems ... not important? The marketing value of this to Anthropic (if Anthropic even cares, this might just be the Bun team selling past the close) is to show that such a rewrite is possible and delivers engineering value. If exactly this…

It isn't clear to me that the price is worth it.

Re: How is the Bun rewrite in Rust going?

#346
post #343

Earlier quoted context omitted.

Author here: I don't need or want another Bun release or an NPM release or anything like that. Like I very clearly say in the article I just got chatting with a peer about the Bun rewrite and I decided to take a look. I'm consistently skeptical about new tech whether it is NoSQL or Blockchain or Serverless. Some of the things I'm skeptical about fail and some succeed.

The bun Port is a phenomenal engineering achievement that would have taken a team of people over a year or two to deliver previously - look at the TypeScript port for example (and they had llms). The fact it's taking a while to release is still insanely fast. I'm sure they may be some bumps. Being skeptical is good and some stuff succeeds and some doesn't - but building tools is still fun and cool, whether it's usefu…

The initial "10 days and $165k" was still a tad optimistic dontchathink?

Re: How is the Bun rewrite in Rust going?

#347
post #34

Earlier quoted context omitted.

I very much doubt they would want to abandon the wider community. They do benefit from others using it. To the contrary, I think any problem with this release would be jumped on harshly so they're being more careful than usual. There's not a rush for the community to move to 1.4 and any issues could poison the community trust.

Like this rewrite did not terminally poison trust?

Has it impacted your use case negatively?

Re: How is the Bun rewrite in Rust going?

#348

Earlier quoted context omitted.

[flagged]

https://bun.com/blog/bun-in-rust This is from July 8, 2026. And while you did link it in your article, what else are you expecting?

The initial post said something like 11 days and $165k in tokens and it's done. The charts in the OP suggest that Something Interesting happened between July 8th and today, burning way more tokens and human labour. Wouldn't you want to know what?

Re: How is the Bun rewrite in Rust going?

#350
post #235

Earlier quoted context omitted.

Author here: I don't need or want another Bun release or an NPM release or anything like that. Like I very clearly say in the article I just got chatting with a peer about the Bun rewrite and I decided to take a look. I'm consistently skeptical about new tech whether it is NoSQL or Blockchain or Serverless. Some of the things I'm skeptical about fail and some succeed.

What are some of your favorite tools or services that you adopted in the past few years?

uv
Post reply on HN