This reads more like Anthropic wanted to hire Jarred and Jarred wants to work with AI rather than build a Saas product around bun. I doubt it has anything to do with what is best for bun the project. Considering bun always seemed to value performance more than all else, the only real way for them to continue pursuing that value would be to move into the actual js engine design. This seems like a good pivot for Jarred personally and likely a loss for bun.

▲

simonw 2 hours ago | parent | next [-]

It doesn't read like that to me at all. This reads to me like Anthropic realizing that they have $1bn in annual revenue from Claude Code that's dependent on Bun, and acquiring Bun is a great and comparatively cheap way to remove any risk from that dependency.

▲

bblaylock 2 hours ago | parent | next [-]

I haven't had any issue moving projects between node, bun, and deno for years. I don't agree that the risk of bun failing as a company affects anthropic at all. Bun has a permissible license that anthropic could fork from, anthropic likely knew that oven had a long runway and isn't in immediate danger, and switching to a new js cli tool is not the huge lift most people think it is in 2025. Why pay for something you are already getting for free and can expect to keep getting for free for at least four years, and buy for less if it fails later?

▲

_jab 2 hours ago | parent | prev | next [-]

This argument doesn’t make much sense to me. Claude Code, like any product, presumably has dozens of external dependencies. What’s so special about Bun specifically that motivated an acquisition?

▲

cobolcomesback an hour ago | parent | next [-]

A dependency that forms the foundation of your build process, distribution mechanisms, and management of other dependencies is a materially different risk than a dependency that, say, colorizes terminal output.

I’m doubtful that alone motivated an acquisition, it was surely a confluence of factors, but Bun is definitely a significant dependency for Claude Code.

▲

rvnx an hour ago | parent [-]

MIT code, let Bun continue develop it, once project is abandoned hire the developers.

If they don't want to maintain; GitHub fork with more motivated people.

	▲	cobolcomesback 25 minutes ago \| parent [-]
		> MIT code, let Bun continue develop it, once project is abandoned hire the developers. Why go through the pain of letting it be abandoned and then hiring the developers anyway, when instead you can hire the developers now and prevent it from being abandoned in the first place (and get some influence in project priorities as well)?

▲

almosthere an hour ago | parent | prev [-]

If they found themselves pushing PRs to bun that got ignored and they wanted to speed up priority on things they needed, if the acq was cheap enough, this is the way to do it.

▲

Karrot_Kream 2 hours ago | parent | prev | next [-]

I'm also curious if Anthropic was worried about the funding situation for Bun. The easiest way to allay any concerns about longevity is to just acquire them outright.

▲

2 hours ago | parent | prev | next [-]

[deleted]

▲

manojlds 2 hours ago | parent | prev | next [-]

Really? What risk is even there?

▲

rco8786 an hour ago | parent | prev [-]

Except bun is OSS, so they could have just forked if something happened

	▲	square_usual an hour ago \| parent [-]
		It's not easy to "just" fork a huge project like Bun. You'll need to commit several devs to it, and they'll have to have Zig and JSC experience, a hard combo to hire for. In many ways, this is an acquihire.

▲

thatoneengineer 2 hours ago | parent | prev [-]

Nah, it reads like the normal logic behind the consulting model for open source monetization, except that Bun was able to make it work with just one customer. Good for them, though it comes with some risks, especially when structured as an acquisition.