Earlier quoted context omitted.
The rewrite part of get to functionally equivalent to the existing zig version in rust did in fact take 11 days based on the available data. When that was done, they spend some time on a ton of new features and hardening and bugfixing that the Rust rewrite enabled. This took additional time.
At the end of the 11 days, reviews raised much use of unsafe blocks. I guess this is much reduced by now, and the effort required on that front should not be rejected from being part of the migration.
Bun 1.4
161–170 of 198 posts
Re: Bun 1.4
#162Earlier quoted context omitted.
The author didn’t care to himself, just merging enormous PRs with “lol” tweets about how github doesn’t display all the changes because there are too many. This is unmaintable mess, and the author himself is struggling already, given how he pushed the release date ten times.
It’s not maintainable by humans because there’s not a single human person who actually wrote any of it. But I guess it’s maintainable by LLMs. Which is part of the anthropic marketing
Re: Bun 1.4
#163This is a huge win for Bun & Anthropic. I've been keeping an eye on Bun development cycle since they announced the Rust rewrite and the huge drama and backlash it generated. They seem to be proving the skeptics wrong with this release.
What exactly has this update led this to be a "huge win"?
Mainly node compatibility though more test coverage and different performance improvements.
Re: Bun 1.4
#164Re: Bun 1.4
#165Re: Bun 1.4
#166Amazing job to the team! We already tried it out and got -50% CPU and -60% Mem usage! https://scrydon.com/insights/2026/08/21/bun-1-4-at-scrydon/
Re: Bun 1.4
#167Earlier quoted context omitted.
It's way late and seriously over budget, hard to call that a success.
~3 months start to finish and the price of 1 engineer for a year, to rewrite a critical infra codebase that tens of millions of user software relies on . Truly the goalposts keep moving. This kind of project would've have been 10x the effort and price a few years ago.
Re: Bun 1.4
#168Earlier quoted context omitted.
We're never going to know how much it cost and how many hours of engineering time it took behind the scenes.
GitHub commits, PRs and issues are public. even their recent buildkite CI logs are public. apparently there's some kind of automated differential fuzzer to discover Node.js incompatibilities, but probably that's behind the curtain. We might never know the exact dollars and cents amount, but we can make pretty well calibrated guesses.
Re: Bun 1.4
#169For me, notably absent from the release changelog and accompanying YouTube video they were excited to trumpet in the blog back in July, and the claim (still) this took 11 days. It's August 20th.
But if they went down in cpu usage and memory usage, removed a memory leak, and are MORE compliant with nodejs... it sounds like a MASSIVE success?
Re: Bun 1.4
#170This is a huge win for Bun & Anthropic. I've been keeping an eye on Bun development cycle since they announced the Rust rewrite and the huge drama and backlash it generated. They seem to be proving the skeptics wrong with this release.