This was an incredible demo for Claude. The runtime hosted Claude Code for months and I never saw the slightest issue. Wholly machine ported. Truly amazing.
Bun 1.4
141–150 of 198 posts
Re: Bun 1.4
#142Earlier quoted context omitted.
How are you deciding that either of these things worked out fine
bun has lesser memory issues, more bug fixes shipped than ever before. same happening across the board with chrome, mozilla etc. twitter has (irrespective of the political turmoil etc.) purely as a technical product added more users, more features etc. to me that seems like it worked out fine.
irrespective of the political turmoil etc
Quite the hand-wave!Re: Bun 1.4
#143This 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.
It's way late and seriously over budget, hard to call that a success.
Re: Bun 1.4
#144Earlier quoted context omitted.
I think around $300-400k, but that does not include the github issue/pr/ci stuff that runs continuously, which could double or triple it. Somewhere, the first two weeks were said to be about $200k.
That total assumes API billing rates, which isn't what Anthropic pays for the inference. So I'm confused why people keep quoting that. It's not representative of what it'd cost for you either because you could use cheaper models.
It is, because this rewrite was marketing for Claude. So it reflects the price for what other companies might need to pay if they want to rewrite something else with similar size.
Re: Bun 1.4
#145This was an incredible demo for Claude. The runtime hosted Claude Code for months and I never saw the slightest issue. Wholly machine ported. Truly amazing.
Re: Bun 1.4
#146Earlier quoted context omitted.
bun has lesser memory issues, more bug fixes shipped than ever before. same happening across the board with chrome, mozilla etc. twitter has (irrespective of the political turmoil etc.) purely as a technical product added more users, more features etc. to me that seems like it worked out fine.
You're celebrating Bun 1.4 on literally day one. I'd suggest waiting for it to hit prod. irrespective of the political turmoil etc Quite the hand-wave!
> irrespective of the political turmoil.
I was mostly concerned with the technical perspective of firing 80% of people by stack ranking. the consensus in HN at the time was that twitter had months left before all production systems burn down, because all the organizational knowledge has left. but seems like firing 80% went just fine for them. which I find fascinating.
Re: Bun 1.4
#147Absolute crickets from the "there's no way LLM's can rewrite Bun to Rust this quickly, it's going to be buggy, it's marketing" crowd Comments here 3 months ago are quite something: https://news.ycombinator.com/item?id=48132488
Sure I’ll bite the obvious bait, why not. > Absolute crickets from the "there's no way LLM's can rewrite Bun to Rust this quickly, it's going to be buggy, it's marketing" crowd > Comments here 3 months ago are quite something: https://news.ycombinator.com/item?id=48132488 Did you… perhaps read the entire comment you just posted? The crowd that was saying “no way they did that in 11 days” sure seems correct given that…
Re: Bun 1.4
#148Re: Bun 1.4
#149So this is kind of a systemd for web developers. All functionality is absorbed into a vibe coded, un-auditable black box. Maybe run it as process 1 in a future ClaudeOS.
As opposed to the famously stable and robust JS ecosystem.
Though it feels like the web tooling is thankfully moving away from JS/Node
EG webpack in js => rspack (rust) typescript in typescript => typescript in go (the loss of bootstrapping is a bit sad but worth it)