Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

How is the Bun rewrite in Rust going?

lockwood.dev

Post reply on HN
Print view View original

361–370 of 412 posts

Re: How is the Bun rewrite in Rust going?

#361

Post by pdimitar »

jbvlkt wrote: post #328
maleldil wrote: post #266

Earlier quoted context omitted.

> How many people have updated Claude/Bun to the latest version By default, Claude Code updates itself all the time without asking for permission, so I'd say most users are on the latest versions.

I do not trust AI agents to run outside sandbox and use them only in dev container. I always use latest version available when I build container (once or twice a month). In my opinion it is to risky to allow auto update for SW which is released several times a week including weekends and is capable of/willing to do script kiddie pranks :-)

Well, OK, you do that. Many others don't. Not sure what your comment adds except saying "not everybody allows audo-update" which is IMO redundant and obvious.

Re: How is the Bun rewrite in Rust going?

#362

Post by nonethewiser »

inigyou wrote: post #249
inglor wrote: 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?

Another functional way to iterate over an array

Re: How is the Bun rewrite in Rust going?

#363

Post by pdimitar »

Banditoz wrote: post #237
giancarlostoro wrote: post #135

Earlier quoted context omitted.

It's just blind AI hate for no rhyme or reason. I've ported projects from one language to the next using Claude Code long before Bun even did this, it's very trivial for an LLM. In the case of Bun though, they have a test suite to run the entire codebase against, and so long as all of those tests pass, there's and drastically more likely chance that its correct.

Seems to be more level skepticism to me. Not "blind hate".

I don't see the multiple dramatic comments to the effect of "this whole thing was a failure" as a level skepticism. While I am sure that one exists, I've noticed another wave of Rust hate hopping on that event which is honestly just sad to watch at this point.

I am sure we are both right though.

Re: How is the Bun rewrite in Rust going?

#364

Post by chmod775 »

dminik wrote: post #229
chmod775 wrote: post #81

Earlier quoted context omitted.

> It took TypeScript a year to go from announcing tsgo to releasing TypeScript 7.0. These are not comparable at all. The bun "rewrite" really is more of a translation of a software that is mainly dogfooded, created with an at best loose regard for a wider ecosystem. TypeScript 7.0. by comparison is not just a translation from one language to another. It's a true rewrite that at the same time has to consider a massive…

It's funny, but a large reason for why Go was chosen was explicitly because it has semantics close to TypeScript and that made it automatable: https://github.com/microsoft/typescript-go/discussions/411#d... > But this wasn't a compiler redesign, and the TypeScript to Go move was far more automatable and more one-to-one in its mapping. So basically the opposite of what you're saying.

IMHO it's not the same car, even if its engine initially was a 1:1 rebuild using other alloys. But you're right I overstated and made myself look dumb (by a lot really - this is nothing like having 2 independent C compilers for instance).

What's taken 1:1, deliberately, was the compiler core. That was almost perfectly 50% of the non-test code. A close translation of that was a starting point, but open CHANGES.md or it's history and you'll see it's quickly diverging even on its surface.

The closest matching, interesting large area of it is probably the checker. Easily recognizable on a function level, even if not being a single file anymore:

https://github.com/microsoft/typescript-go/tree/main/interna...

https://raw.githubusercontent.com/microsoft/TypeScript/refs/... (The TS file is 3MB and github won't display it inline)

You'll find a lot of the same data structures (as far as that's possible in a TS-to-Go translation + ripples from areas that were more heavily changed) and functions lying around, just in slightly different places. Because of the AST changes and TS/Go differences on a line-level each function might look different, but where there is a loop in the TS one, there's probably one in Go.

The other half of the project is heavily changed or completely new/different (like concurrency, less weird language service).

Re: How is the Bun rewrite in Rust going?

#365

Post by hungryhobbit »

brabel wrote: post #257
interroboink wrote: post #189

Earlier quoted context omitted.

This might be terminology that's used differently in different places. For instance, in video games it is extremely common to use "postmortem" to mean "post-shipping." Example: https://blog.codinghorror.com/game-development-postmortems/ Note the dual emphasis on both "what went right" and "what went wrong," not just one or the other.

But postmortem is literally “post death” in Latin. It’s synonymous with autopsy! I know people misuse borrowed words all the time, but come on?!

Languages change. That word "literally", which you just used, meant one thing for decades (centuries?) ... and now it also (literally) means the exact opposite.

You can be the crabby old guy complaining about how the youth ruined English ... or you can accept that languages aren't immutable, and that the meaning of postmortem is no longer it's literal meaning.

Re: How is the Bun rewrite in Rust going?

#366

Post by solid_fuel »

egorfine wrote: post #193
Jarred wrote: post #148

Bun’s Rust rewrite shipped in Claude Code over a month ago and barely anyone noticed. Claude Code is widely used. The Rust rewrite is going well overall. In the Bun v1.4 video, I promised a certain number of newly passing Node.js tests were added to force us to improve compatibility, and that number is not true yet. The release is delayed until it is true. The PRs to make it true are up but not merged yet. Most likel…

Any chance for 1.3.15 with bugfixes for the rest of us?

They declared bankruptcy on the original code base so hard that they decided to chuck it all in the trash. I wouldn't hold my breath expecting support for their existing users.

Re: How is the Bun rewrite in Rust going?

#367

Post by WhitneyLand »

tomlockwood wrote: post #196
inglor wrote: 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 problem is what you’re skeptical about, the true cost, is probably the least important part.

Did it really cost $1 million instead of the 150k that’s been floating around?

If you don’t like the price now just give it some time.

The point is that these kind of heroics can actually work now and they’re only going to get cheaper.

I don’t mean to sound negative about what you wrote, it was an interesting read.

Re: How is the Bun rewrite in Rust going?

#368

Post by chmod775 »

skeledrew wrote: post #281
chmod775 wrote: post #177

Earlier quoted context omitted.

> This seems self-contradictory. It's not. Passing an existing test suite just moves the optimistic lower bound to incidental compatibility, it doesn't move it to intentional - "regard" implies you gave it thought. Plus, it's not just about code: it's also about giving the ecosystem a migration path. Dumping 500k LOC on people and discontinuing development of the zig version effective immediately (there hasn't been a…

That "incidental compatibility" point is a good place to start. Unless there are serious gaps in the test suite, one can have high confidence that there's no regression from the pre-fork version in documented behavior. What kind of migration path beyond 0 regression do you think is needed? And if the latest Zig version is no longer available, how were at least 2 forks based on it submitted to HN? And what kind of rel…

> And if the latest Zig version is no longer available, how were at least 2 forks based on it submitted to HN?

Where did I ever claim this? I said they don't even have the Zig build script in their repo anymore - they're clearly not intending to make any more changes to it, even if the code is still lying there next to the Rust code.

> If the userbase is as miniscule as you imagine then your criticisms are essentially meaningless.

They're not criticisms, they're observations. The point is that the challenge is not comparable - because TypeScript's existing ecosystem is part of their challenge.

Re: How is the Bun rewrite in Rust going?

#369

Post by bentocorp »

Jarred wrote: post #148

Bun’s Rust rewrite shipped in Claude Code over a month ago and barely anyone noticed. Claude Code is widely used. The Rust rewrite is going well overall. In the Bun v1.4 video, I promised a certain number of newly passing Node.js tests were added to force us to improve compatibility, and that number is not true yet. The release is delayed until it is true. The PRs to make it true are up but not merged yet. Most likel…

Ok, so you've just admitted that you have deployed thousands of lines of likely non-human reviewed LLM generated code (Bun's rust rewrite) to millions of client machines (via the Claude Code app auto-update) with significant local client access credentials, in a relatively quick and rushed manner.

What's stopping the LLM from having unscrupulously injected something nefarious into the codebase that you are unaware of?

What's stopping future updates from the LLM from doing the same?

Are you aware of the potential ramifications of deploying thousands of lines of non-human reviewed code to millions of users machines?

Are you happy to be personally responsible for the horrendous outcomes that could occur in these situations?

Re: How is the Bun rewrite in Rust going?

#370

Post by CrimsonRain »

tomlockwood wrote: post #163
Jarred wrote: post #148

Bun’s Rust rewrite shipped in Claude Code over a month ago and barely anyone noticed. Claude Code is widely used. The Rust rewrite is going well overall. In the Bun v1.4 video, I promised a certain number of newly passing Node.js tests were added to force us to improve compatibility, and that number is not true yet. The release is delayed until it is true. The PRs to make it true are up but not merged yet. Most likel…

[flagged]

Are you jealous? You sound jealous. And angry too.
Post reply on HN