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

201–210 of 412 posts

Re: How is the Bun rewrite in Rust going?

#201

Post by swiftcoder »

busterarm wrote: post #168
ambicapter wrote: post #159

Earlier quoted context omitted.

The job-hopping followed from companies not investing in their engineers, not the other way around. It was billed as the only way to get a promotion (which usually would come every 1-2 years).

I've been in this industry for a few decades at this point and I was around when this meme was started. It was purely about maxing your compensation because changing jobs nets you more than promotions & raises. I've never met an engineer in my life who truly earned a promotion every year and very few every two. Very few companies have org charts that even support that or have that many levels. This logic/advice only…

> It was purely about maxing your compensation because changing jobs nets you more than promotions & raises.

You don't view it as a problem that companies consistently compensate new hires higher than they are their experienced employees?

Hell, I would have been perfectly happy to never change employers in my entire career to date, if my salary had anywhere near kept pace with my peers who were job-hopping.

Re: How is the Bun rewrite in Rust going?

#202

Post by atonse »

amazingamazing wrote: post #60
jeltz wrote: post #37

Earlier quoted context omitted.

They bought the maintainers, not the code.

Why though? Isn't AI supposed to take care of such things?

Because even when the AI is really good at writing code, you still have to know what to ask it, how to direct it, have product taste, etc.

Otherwise all of us would just be able to build bun via a prompt.

Re: How is the Bun rewrite in Rust going?

#203

Post by dzhar11 »

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…

Jarred, thank you for working on Bun. Many "vibe coded" :D projects start strong and are later abandoned (like potentially Anthropic C), so I understand why people worry about Bun's future. I hope Bun lasts for many years, like GCC. Bun is fast and great to use.

Re: How is the Bun rewrite in Rust going?

#204

Post by simonw »

tomlockwood wrote: post #200
simonw wrote: post #195

Earlier quoted context omitted.

In this sentence, sure: > Anthropic is dogfooding this, the machine is still ticking along, and Anthropic employees are directly involved. The problem is that your article's central claim is that there hasn't been a Bun release since the Rust rewrite - which can be read as implying that the rewrite hasn't been used in production. But it's been used in production on millions of machines running Claude Code for over a…

I link to Jarred's writeup on bun.com, where you'll note he mentions that its being used on Prisma and Claude Code. I don't agree that using something in a very specific environment is the same as a wide release. I trust readers will either know the backstory or read the articles I link to. Such is life if they don't.

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."

Re: How is the Bun rewrite in Rust going?

#205

Post by hombre_fatal »

nicce wrote: post #174
Aurornis wrote: post #128

Earlier quoted context omitted.

> Its one thing to get a head start using this trick, its another to actually learn the code of your rewrite. I worked for a startup that stopped feature development and did a complete rewrite of a huge codebase. I was assigned to a side project during this time and missed the entire rewrite process. I came back to a completely rewritten codebase. There was almost no learning curve, despite being in an entirely diffe…

> There was almost no learning curve, despite being in an entirely different language. The core architecture, data structures, and concepts were the same. > If you read the Bun blog post on how they did it, their rewrite was similar: The first step was getting it into a new language, not rearchitecting it from scratch They eventually might regret this, when they are trying to get rid of the last lines of unsafe code.…

I doubt it.

If this were a major issue then you'd have to always nail your Rust architecture correctly from day 1 to handle future unknowns, and this isn't the case.

More importantly, LLMs are more than capable of figuring out how to rearchitect code and they have no problem making sweeping refactors for you, especially throwaway experimental ones that were way too expensive to do not long ago.

Re: How is the Bun rewrite in Rust going?

#206

Post by bigstrat2003 »

Atotalnoob wrote: post #126
rienbdj wrote: post #44

Earlier quoted context omitted.

Anyone know why? Can’t CC run on any JS runtime?

Yes, but it’s slower on non-bun runtimes. Nowadays, I believe they bundle bun with CC They chose to use a react rendering to native TUI renderer, which was a source of a lot of performance issues. AFAIK, they have written a new renderer.

> They chose to use a react rendering to native TUI renderer, which was a source of a lot of performance issues.

That's such a stupid engineering choice that it really makes one question if the people working at Anthropic have any software engineering ability at all. There's no excuse for running React in a freaking TUI.

Re: How is the Bun rewrite in Rust going?

#207

Post by tomlockwood »

simonw wrote: post #204
tomlockwood wrote: post #200

Earlier quoted context omitted.

I link to Jarred's writeup on bun.com, where you'll note he mentions that its being used on Prisma and Claude Code. I don't agree that using something in a very specific environment is the same as a wide release. I trust readers will either know the backstory or read the articles I link to. Such is life if they don't.

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."

Please feel free to write an article that corrects my mistakes.

Re: How is the Bun rewrite in Rust going?

#208

Post by TiredOfLife »

chmod775 wrote: post #81
muglug wrote: post #47

Earlier quoted context omitted.

A major rewrite in another language is also unusual for this project. It took TypeScript a year to go from announcing tsgo to releasing TypeScript 7.0. That work was done in parallel; here the work is being done serially — and it’s likely to take much less than a year for a new release.

> 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…

TypeScript 7.0 was literally a line by line translation. With essential features necessary for adoption still like a year off.

Re: How is the Bun rewrite in Rust going?

#209

Post by root_axis »

simonw wrote: post #195
tomlockwood wrote: post #190

Earlier quoted context omitted.

I mention Anthropic dogfooding this in the article.

In this sentence, sure: > Anthropic is dogfooding this, the machine is still ticking along, and Anthropic employees are directly involved. The problem is that your article's central claim is that there hasn't been a Bun release since the Rust rewrite - which can be read as implying that the rewrite hasn't been used in production. But it's been used in production on millions of machines running Claude Code for over a…

> which can be read as implying that the rewrite hasn't been used in production.

Well it hasn't. "Production" for a language runtime means being generally available for arbitrary use. The engineers that built the runtime using it to release one closed source binary to the public is, at best, an extremely narrow beta test.

Re: How is the Bun rewrite in Rust going?

#210

Post by sroussey »

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?

Yeah, 1.3.14 has some bad regressions. 1.3.11 is ideal for tests CI. Or canary. For production, I don’t have any advice. There will be no 1.3.15.
Post reply on HN