5 ms·
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 th
by Jarred 2mo 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.
- tomlockwood 2mo ago[flagged]
- TheRealPomax 2mo agoEither you mean retrospective, or you're being unnecessarily mean for something that's been getting quite a lot update reports, just on a social medium you probably don't use =P
- tomlockwood 2mo agoI thought it was a fairly common turn of phrase! https://blog.codinghorror.com/the-project-postmortem/ https://blog.codinghorror.com/the-project-postmortem/
- TheRealPomax 2mo agoA postmortem is for reflecting on something that went so wrong you had to kill it, and you want to objectively describe what led to that, and what lessons can be learnt from the failure. A retrospective is just the reflecting part, without implying you believe it is going to fail and you're looking for some schadenfreude ;)
- tomlockwood 2mo agoFrom the article: > The goal of a postmortem is to draw meaningful conclusions to help you learn from your past successes and failures. Despite its grim-sounding name, a postmortem can be an extremely productive method of improving your development practices.
- interroboink 2mo agoThis 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/ 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.
- brabel 2mo agoBut postmortem is literally “post death” in Latin. It’s synonymous with autopsy! I know people misuse borrowed words all the time, but come on?!
- interroboink 2mo ago> is literally “post death” in Latin Yes; I think what I described matches that meaning? Post-death, as in: "it's over," "activity has halted," "no more work being done." Death does not necessarily have a bad/negative connotation. It's just the end of something. This is in contrast to the original comment: "something that went so wrong you had to kill it." Death does not imply something went wrong or that it happened forcefully. I guess "autopsy" generally is talking about "finding the cause of death" so maybe that has a more negative connotation ("something (bad) happened, causing death, let's find it"). Ah, words with their fuzzy meanings (:
- WD-42 2mo ago> Post-death, as in: "it's over," "activity has halted," "no more work being done” Which makes even less sense as we all know software is never done, unless it truly is dead.
- vitorfblima 2mo agoIn the context of a game it applies. A game can be "done", as in shipped, no more updates, patches, etc.
- 2mo ago
- dogleash 2mo agoI've been reading people use "postmortem" to describe software retrospectives for like... 15+ years. Mostly in the opensource, or marketing-blog spaces. The detailed investigation and fix report was a favorite genre of blogpost. And if someone's bragging about the design of an enhancement, or investigating a bug, then the overall product isn't dead. They're (usually) not talking shit to anyone. It's the bug that's dead. Or security indecent that's over. Or a schedule milestone that's "dead and burred". It's a 1 chili pepper level of spicy to use a slang term that relates to death. I'd never read it as hoping someone fails. I think people let the corpotalk center of the brain overreact to anything that's not couched in euphemism.
- wrs 2mo agoIn the specific case of ship retrospectives, I prefer to call them “postpartums”.
- ModernMech 2mo agoI guess they’re saying their shipped code is DOA?
- dagmx 2mo agoA post mortem is a very common term in many industries on how something went after you shipped it. You’re taking it very literally here, it does not involve anything being dead or killed. We’ve used this in the software, games, film and construction industries for decades at this point. Substitute Mortem for Ship and that’s how people use it.
- aleksandrm 2mo agohttps://bun.com/blog/bun-in-rust 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?
- jojobas 2mo agoThe 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?
- CrimsonRain 2mo agoAre you jealous? You sound jealous. And angry too.
- lantry 2mo agoAny comment on the costs estimated in the article? especially the buildkite costs?
- Jarred 2mo agoCI 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.
- JustSkyfall 2mo agoHow come Bun uses Buildkite instead of self-hosting the CI infra?
- simonw 2mo agoPresumably because they "build for [macOS, Linux, FreeBSD, Android, Windows] x [ARM64, x64]" and self hosting all of that would be time-consuming and expensive.
- CamouflagedKiwi 2mo agoProbably because they don't want to self-host Windows or MacOS servers when they can pay someone else to do that for them (or Linux ones, I assume that is within their wheelhouse for production but CI is a bit of a different beast to model inference).
- Jarred 2mo agoIt spawns ephemeral EC2/Azure instances, which is a lot cheaper than the GitHub actions runners we used before that. We shard to a lot of machines for tests and I’d be worried about running out if we used dedicated servers. BuildKite is fine but I wouldn’t be that surprised if we move off of BuildKite to a custom thing at some point. Months ago, we switched from CMake to a handrolled typescript build system and it made our builds faster and simpler.
- inglor 2mo agoTake 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 2mo agoAuthor 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 2mo agoWhat are some of your favorite tools or services that you adopted in the past few years?
- tomlockwood 2mo agouv
- throw1234567891 2mo agoThat’s a great approach. No matter what you will always find a reason to be positively surprised!
- inglor 2mo agoThe 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 :)
- egorfine 2mo agoAny chance for 1.3.15 with bugfixes for the rest of us?
- sroussey 2mo agoYeah, 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.
- solid_fuel 2mo agoThey 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.
- dzhar11 2mo agoJarred, 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 2mo agoAnthropic'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.
- sfink 2mo ago> What it actually proved is up for debate. I guess I'm debating, but it seemed clear enough to me? It proved that AI models and their harnesses are to the point where you can give them some work to do and leave them unattended for a long time, and they'll keep doing productive work for quite a while. This was a novel thing, and quite unclear, at the time the experiment was performed. Obviously, the word "productive" is doing a lot of work there, but in my understanding the intention was nowhere near "commercially viable" or "practically useful", it was more like "not doing stupid shit like writing comments of the form 'This file contains the implementation implementation implementation implementation implementation implementation implementation implementation implementation implementation implementation implementation implementation ...'". Maybe somewhere in the vicinity of "either passing more tests or generating more valid tests"?
- dzhar11 2mo agoThe issue is that the Claude's C Compiler repository does not explicitly identify the project as a proof of concept. It was largely produced by one person directing Claude, and Bun's Rust rewrite also seems to have been driven by roughly one person using Claude Code. That similarity is what worries me. Bun's rewrite could also turn out to be proof of concept.
- wesselbindt 2mo agoIn Dutch there's a saying, "wij van wc eend adviseren wc eend", and it fits perfectly.
- achenet 2mo agoFrenchman 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 2mo agoIt 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.
- card_zero 2mo agoThe Toilet Duck brand exists in English. Canard-WC in French, even.
- tialaramex 2mo agoActually the existence of the French name is confusing for English speakers as although many would know enough school French to get "canard" == "duck" if prompted, in English this word ends up meaning some sort of fabrication or hoax, apparently from an old French joke where somehow that punchline of that joke was popularized in England so long ago we don't have records. Human culture is weird. So the first thing an English native might get from "Canard WC" is probably hoax toilet, I expect the duck imagery of the product would bring the "canard" == "duck" meaning across though.
- jamesfinlayson 2mo agoI probably should have figured part of it out from my basic German, but I guess the Dutch don't capitalise nouns?
- deleted 2mo ago[deleted]
- alkr-g234 2mo agoWe 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 2mo 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.
- jbvlkt 2mo agoI 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 :-)
- pdimitar 2mo agoWell, 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.
- thayne 2mo agoThat's not surprising. Claude code is buggy enough, and releases break things often enough, that I wouldn't expect users to distinguish bugs introduced by switching to rust-based-bun from the normal garden variety bugs.
- denverllc 2mo agoI’ve come to just expect that my CC instance will randomly “blank” and that I have to resize my terminal / use page up/page down to get it to show again. Supposedly they used a game engine to render their TUI but I’ve never had an FPS game do that.
- Daviey 2mo agoThey drive the TUI from the same thread that actual does stuff.. causing frequent freezes. No GUI developer would ever put this on the same thread.
- FridgeSeal 2mo agoJust ask Claude to fix it, what’s the problem??????? /s
- dimava 2mo ago"Claude did implement multithreading in JS but we don't want to mantain a fork of WebKit" - jared apparently
- whyhnwhy 2mo ago[dead]
- AlexErrant 2mo agoI can count the number of times an @ file reference doesn't autocomplete on a hundred hands. Or how a rewind won't reset the "is this file Read" marker. Or how a Branch (forking a convo) takes literally 5+secs to run. Or how a slashcommand that's user-only will not work if its in the middle of a prompt. Or how ctrl-r search will match results that don't include any search terms. Or how you can't resume a branch given its session id. Yes Boris, tell me more about how "coding is solved". Edit: literally just now, while writing a claude code hook, opus5 gave me this LOC because apparently the changelog and what's in the transcripts _differs_; great docs d00ds. # Present only for a subagent's calls. Both spellings accepted: the changelog # names `agent_id`, transcripts use `agentId`, and we need not care which lands. agent=$(printf '%s' "$input" | jq -r '.agent_id // .agentId // empty')
- solid_fuel 2mo ago[flagged]
- yard2010 2mo agoJarred thank you for doing the impossible over and over. Bun is such a fun thing to use after years of npm. Good luck with your quests! Have fun
- up2isomorphism 2mo agoIf actually anyone noticed, then it is a pretty bad move. Also “going well overall “ does not answer the author’s observations either.
- HAL3000 2mo agoI noticed, I started getting memory leaks suddenly and it restarted the process in long sessions because of limitation of environment limit.
- bentocorp 2mo agoOk, 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?
- marcins 2mo agoClaude Code has been written with Claude Code for a long time - that ship has long sailed.
- bjourne 2mo agoTHE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. I guess they put it in capitals for a reason.
- bentocorp 2mo ago