Live data from Hacker News

I am worried about Bun

wwj.dev

61–70 of 368 posts

Re: I am worried about Bun

#61
post #51

I wonder why Anthropic chose to spend money on Bun when they could have easily spend that resource on Go which is fairly easy to use and fast. I'm sure their SWEs could easily everything things in Go. Anyone have insight on why?

I doubt those SWEs could have used anything other than JS.

Re: I am worried about Bun

#62
post #5

Why did you have to stop using Cursor? I ask this as someone that uses Cursor, but recently at a conference I heard it referred to negatively several times - but in a very vague sense. I don't really have a dog in the fight, I'm using it because thats what the other dev I work with is using.

There is the SpaceX acquisition rumor, but that's not why. I only use Cursor through the CLI, and while the UX of the CLI is pretty bad, I've found their harness (the prompts they use and orchestration of LLMs) to be nothing short of incredible. I can't comment on their agent development environment given I haven't spent a lot of time with it. The reason I'm moving away from Cursor is cost. Unfortunately, if you want…

I agree with your assessment that the harness is incredible and so I get a ton of mileage out of Auto + Composer 2. This is my workhorse.

Admittedly, with Opus 4.6+, GPT 5.5 I just haven't used them much and as I gain more experience I can see what the hype is all about. But to me, the answer isn't $200 max plan, it's bifurcating the work. Call me a spendthrift!

Re: I am worried about Bun

#63
post #39

I disagree with the overall premise: Before the acquisition, Bun had to figure out how to monetize at some point. Now, even though their parent company does some shitty practices with their other software (claude code), it's a stretch to assume this will also translate into making Bun worse: Being worried makes sense but I remain optimistic about Bun. Especially given the context of both of these different context: C…

> Before the acquisition, Bun had to figure out how to monetize at some point. I think it is insane that people got into a situation where they had committed to a javascript runtime that had to "figure out how to monetize at some point". It is also bizarre that some people are still hopeful despite it being acquired by one of the most enormously unprofitable companies in the most enormously unprofitable sectors of ou…

> I think it is insane that people got into a situation where they had committed to a javascript runtime that had to "figure out how to monetize at some point".

Why? What's the risk? It's open source. Also, speaking of open source, we are happy to commit to open source projects that have no monetization, nor any plans to ever monetize.

Re: I am worried about Bun

#64

I disagree with the overall premise: Before the acquisition, Bun had to figure out how to monetize at some point. Now, even though their parent company does some shitty practices with their other software (claude code), it's a stretch to assume this will also translate into making Bun worse: Being worried makes sense but I remain optimistic about Bun. Especially given the context of both of these different context: C…

You might be underestimating the effect that corporate policies and culture have on the product.

Some teams have a push now to go all in on AI; don't even look at the code. I've seen this in action and the results are probably what you'd expect. Works great at some level, but as complexity accumulates (especially across a team with different "technical vocabularies"), the end result is compounding complexity and mistakes and no person or team knows how the software actually works.

No human testing of software or QA; unit + integration + give AI control over the browser/tool. Yes, this how some teams are moving forward now. So some of this may be that Anthropic's culture will end up causing shifts in how the Bun team operates and thinks.

If this type of culture and mindset becomes the norm, I think either the models have to get a lot better or the software quality is going to decline.

Matt Pocock has a great talk here: https://youtu.be/v4F1gFy-hqg

    "Code is not cheap. Bad code is the most expensive it's ever been. Because if you have a codebase that's hard to change, you're not able to take advantage of all of the bounty that AI can offer.  Because AI in a good codebase actually does really, really well."
Once bad code starts to compound on itself, it's going to be really hard to break out of it.

Re: I am worried about Bun

#65

I disagree with the overall premise: Before the acquisition, Bun had to figure out how to monetize at some point. Now, even though their parent company does some shitty practices with their other software (claude code), it's a stretch to assume this will also translate into making Bun worse: Being worried makes sense but I remain optimistic about Bun. Especially given the context of both of these different context: C…

> Now, even though their parent company does some shitty practices with their other software (claude code), it's a stretch to assume this will also translate into making Bun worse: Being worried makes sense but I remain optimistic about Bun.

Can you point to any examples of a company with shitty practices buying one without shitty practices that didn't end up with the shitty practices diffusing through the newly-acquired company within a couple of years?

Re: I am worried about Bun

#66
post #53
post #51

I wonder why Anthropic chose to spend money on Bun when they could have easily spend that resource on Go which is fairly easy to use and fast. I'm sure their SWEs could easily everything things in Go. Anyone have insight on why?

One of them is a much more efficient but obscure programming language from a competitor, the other is what the web is built on.

In what world is Go an obscure programming language??

Re: I am worried about Bun

#67

I love coding with bun. It comes with everything. For my projects I don’t even need any additional dependencies. I use vanilla dom and sqlite

The built-in sqlite and testing functionality is the reason I started using it over pnpm/Node.

Node has both built-in sqlite and testing functionality. Lots of reasons to like bun! But these two are interesting ones...

Re: I am worried about Bun

#69
post #59
post #51

I wonder why Anthropic chose to spend money on Bun when they could have easily spend that resource on Go which is fairly easy to use and fast. I'm sure their SWEs could easily everything things in Go. Anyone have insight on why?

Is Claude better with Javascript than it is with Go code? Seems like it could be true.

I don’t believe so, Go has simple rules, snd in my experience Claude is excellent at writing all the boilerplate needed

Re: I am worried about Bun

#70
post #51

I wonder why Anthropic chose to spend money on Bun when they could have easily spend that resource on Go which is fairly easy to use and fast. I'm sure their SWEs could easily everything things in Go. Anyone have insight on why?

If I had to guess, it comes down to speed of iteration. Claude Code is built on JavaScript, so Bun aligns well with their current stack.

Switching to Go or Rust would only make sense if performance were the main priority, which doesn’t seem to be the case. Their current setup lets them ship quickly. A rewrite in Go would likely slow that down.

Codex moved to Rust, and you can see the trade-off. Performance improved, but release velocity dropped. They’re also still catching up to Claude Code, so they don’t face the same pressure to ship as fast.

Post reply on HN