Comment by Jarred

5 hours ago

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 likely next Tuesday we’ll do the release of 1.4.

36 comments

Jarred

Reply
inglor  4 hours ago

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 "angry" blog post.

(I'm a Node.js maintainer)

  • tomlockwood  4 hours ago

    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.

    • da02  2 hours ago

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

lantry  4 hours ago

Any comment on the costs estimated in the article? especially the buildkite costs?

  • Jarred  4 hours ago

    CI has always been expensive for Bun including before the acquisition. We build for [macOS, Linux, FreeBSD, Android, Windows] x [ARM64, x64] and then run tests on multiple Linux distros with multiple shards, multiple macOS versions and Windows for each architecture.

    We recently started cross-compiling all the builds on Linux arm64 and that made it a little faster (I wrote a CLI tool to download the correct macOS headers for cross-compilation). We also have a daily cron job that asks claude to make the slowest tests faster while adding more assertions.

    • sandeepkd  1 hour ago

      I think the question for CI costs is still out there. While I do not think it should be in tunes of thousands a day but thats the skepticism presented in the article. True costs are really important to make a good decision in situations like this. One has to consider the fact that lots of people are going to use these numbers to justify the rewrite in future.

wesselbindt  3 hours ago

In Dutch there's a saying, "wij van wc eend adviseren wc eend", and it fits perfectly.

  • tptacek  2 hours ago

    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.

  • achenet  3 hours ago

    Frenchman here, I Google Translated that and it says

    "We at WC Duck recommend WC Duck"... I'm left scratching my head, if you'd care to spell out what the saying means for non-Dutch I'd appreciate it :)

    • wesselbindt  3 hours ago

      It was a commercial slogan for a toilet cleaning agent. An English equivalent would be "mr clean recommends you use mr clean". Today, it is used to point out when someone tells you they themselves delivered good work. Anytime you'd use the meme of Obama giving himself a medal, you could use this phrase.

      1 reply →

alkr-g234  2 hours ago

We would need to know at least:

- How many people have updated Claude/Bun to the latest version.

- How many subscribers care about reporting issues. Most of them are forced to use the tool against their will and have mentally checked out already. Why report issues if your employer values slop code anyway. Just log the hours and keep your head down. Maybe it is not expedient for the AI narrative to report issues!

- How many subscriptions are real vs. bulk distiller accounts.

- If subscriber numbers are inflated.

Judging by the weird Claude Code Github issues page, there are suspiciously few new issues: about 2 to 3 a day only vs. alleged subscriber numbers of 4 million.

  • maleldil  1 hour ago

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

dzhar11  3 hours ago

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.

  • maleldil  1 hour ago

    Anthropic's C compiler was a proof of concept[1], so it makes sense that it was abandoned.

    [1] What it actually proved is up for debate.

egorfine  4 hours ago

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

  • sroussey  3 hours ago

    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.

tomlockwood  5 hours ago

> The Rust rewrite is going well overall.

I look forward to the postmortem!