zlacker

[parent] [thread] 43 comments
1. jjorda+(OP)[view] [source] 2025-12-02 18:24:39
I don't really see how Bun fits as an acquisition for an AI company. This seems more like "we have tons of capital and we want to buy something great" than "Bun is essential to our core business model".
replies(5): >>nuruma+j >>gkober+Q >>sankal+T >>rvz+d2 >>logsr+ht
2. nuruma+j[view] [source] 2025-12-02 18:25:42
>>jjorda+(OP)
Looks like they are acquiring the team rather than the product
replies(1): >>simonw+w
◧◩
3. simonw+w[view] [source] [discussion] 2025-12-02 18:26:13
>>nuruma+j
No, they're clearly acquiring the technology. They're betting Claude Code on Bun, they have an invested interest in the health of Bun.
replies(2): >>LunaSe+n1 >>gianca+E1
4. gkober+Q[view] [source] 2025-12-02 18:27:28
>>jjorda+(OP)
If Anthropic wants to own code development in the future, owning the full platform (including the runtime) makes sense.

Programming languages all are a balance between performance/etc and making it easy for a human to interact with. This balance is going to shit as AI writes more code (and I assume Anthropic wants a future where humans might not even see the code, but rather an abstraction of it... after all, all code we look at is an abstraction on some level).

replies(4): >>singul+I1 >>Kwpols+s4 >>hobofa+G4 >>Booris+k7
5. sankal+T[view] [source] 2025-12-02 18:27:38
>>jjorda+(OP)
Does this acquisition mean Claude Code the CLI is more valuable than entiriety of Bun?
replies(3): >>gehsty+O1 >>simonw+M7 >>throwa+9n
◧◩◪
6. LunaSe+n1[view] [source] [discussion] 2025-12-02 18:29:15
>>simonw+w
Why would they want to bet on nascent technology whereas Node.js bas existed for a god 15 years?
replies(3): >>stonog+c2 >>jitl+C5 >>simonw+97
◧◩◪
7. gianca+E1[view] [source] [discussion] 2025-12-02 18:30:19
>>simonw+w
That was my thinking is, this would be useful for Claude Code.
◧◩
8. singul+I1[view] [source] [discussion] 2025-12-02 18:30:26
>>gkober+Q

   "the full platform"
there are more languages than ts though?

Acquisition of Apple Swift division incoming?

replies(4): >>tomash+r2 >>bigyab+q3 >>gianca+v3 >>gkober+Nd
◧◩
9. gehsty+O1[view] [source] [discussion] 2025-12-02 18:30:35
>>sankal+T
It certainly generated more revenue, so this is not surprising?
replies(1): >>re-thc+x2
◧◩◪◨
10. stonog+c2[view] [source] [discussion] 2025-12-02 18:32:05
>>LunaSe+n1
Because Microsoft already owns that.
replies(1): >>Octoth+24
11. rvz+d2[view] [source] 2025-12-02 18:32:06
>>jjorda+(OP)
It does actually.

Claude Code is a 1B+ cash machine and Anthropic directly uses Bun for it.

Acquiring Bun lowers the risk of the software being unmaintained as Bun made $0 and relied on VC money.

Makes sense, but this is just another day in San Francisco of a $0 revenue startup being bought out.

◧◩◪
12. tomash+r2[view] [source] [discussion] 2025-12-02 18:33:26
>>singul+I1
TypeScript is the most popular programming language on the most popular software hosting platform though, owning the best runtime for that seems like it would fit Pareto's rule well enough:

https://github.blog/news-insights/octoverse/octoverse-a-new-...

◧◩◪
13. re-thc+x2[view] [source] [discussion] 2025-12-02 18:34:14
>>gehsty+O1
> It certainly generated more revenue, so this is not surprising?

Anything is greater than 0

replies(1): >>dangoo+8x1
◧◩◪
14. bigyab+q3[view] [source] [discussion] 2025-12-02 18:37:23
>>singul+I1
Why acquire Swift when you can write iOS apps in Typescript instead?
replies(1): >>gianca+z3
◧◩◪
15. gianca+v3[view] [source] [discussion] 2025-12-02 18:37:52
>>singul+I1
According to a JetBrains dev survey (I forget the year) roughly 58% of devs deploy to the web. That's a big money pie right there.
replies(1): >>vlovic+r4
◧◩◪◨
16. gianca+z3[view] [source] [discussion] 2025-12-02 18:38:12
>>bigyab+q3
Which would use something like Bun ;)
◧◩◪◨⬒
17. Octoth+24[view] [source] [discussion] 2025-12-02 18:39:56
>>stonog+c2
Are you referring to node? MS doesn't own that. It's maintained by Joyent, who in turn is owned by Samsung.
replies(1): >>simonw+C7
◧◩◪◨
18. vlovic+r4[view] [source] [discussion] 2025-12-02 18:41:14
>>gianca+v3
Bun isn’t on the web. It’s a server runtime.
replies(1): >>gianca+S4
◧◩
19. Kwpols+s4[view] [source] [discussion] 2025-12-02 18:41:16
>>gkober+Q
They will own it, and then what? Will Claude Code end every response with "by the way, did you know that you can switch to bun for 21.37x faster builds?"
replies(1): >>Booris+68
◧◩
20. hobofa+G4[view] [source] [discussion] 2025-12-02 18:42:31
>>gkober+Q
Even outside of code development, Anthropic seems to be very strongly leaning into code interpreter over native tool calling for advancing agentic LLM abilities (e.g. their "skills" approach). Given that those necessitate a runtime of sorts, owning/having access to a runtime like Bun that could e.g. allow them to very seamlessly integrate that functionality into their products better, this acquisition doesn't seem like the worst idea.
◧◩◪◨⬒
21. gianca+S4[view] [source] [discussion] 2025-12-02 18:42:57
>>vlovic+r4
It's a JS runtime, not specifically servers though? They essentially can bundle Claude Code with this, instead of ever relying on someone installing NodeJS and then running npm install.

Claude will likely be bundled up nicely with Bun in the near future. I could see this being useful to let even a beginner use claude code.

Edit:

Lastly, what I meant originally is that most front-end work happens with tools like Node or Bun. At first I was thinking they could use it to speed up generating / pulling JS projects, but it seems more likely Claude Code and bun will have a separate project where they integrate both and make Claude Code take full advantage of Bun itself, and Bun will focus on tight coupling to ensure Claude Code is optimally running.

replies(2): >>vlovic+nd >>rounce+bf
◧◩◪◨
22. jitl+C5[view] [source] [discussion] 2025-12-02 18:45:49
>>LunaSe+n1
it starts fast and does better job than nodejs for their product
◧◩◪◨
23. simonw+97[view] [source] [discussion] 2025-12-02 18:51:07
>>LunaSe+n1
Because they needed something that could produce a single binary that works on every platform. They started shipping Claude Code with Bun back in July: https://x.com/jarredsumner/status/1943492457506697482
replies(1): >>LunaSe+ke
◧◩
24. Booris+k7[view] [source] [discussion] 2025-12-02 18:52:12
>>gkober+Q
It doesn't make sense, and you definitely didn't say why it'd make sense... but enough people are happy enough to see the Bun team reach an exit (especially one that doesn't kill Bun) that I think the narrative that it makes sense will win out.

I see it as two hairy things canceling out: the accelerating trend of the JS ecosystem being hostage to VCs and Rauch is nonsensical, but this time a nonsensical acquisition is closing the loop as neatly as possible.

(actually this reminds me of Harry giving Dobby a sock: on so many levels!)

◧◩◪◨⬒⬓
25. simonw+C7[view] [source] [discussion] 2025-12-02 18:53:49
>>Octoth+24
Joyent handed Node.js over to a foundation in 2015, and that foundation merged into the JS Foundation to become the OpenJS Foundation in 2019.

I'm not sure if Joyent have any significant role in Node.js maintenance any more.

replies(1): >>Octoth+79
◧◩
26. simonw+M7[view] [source] [discussion] 2025-12-02 18:54:33
>>sankal+T
Claude Code has an annual run rate of $1bn. Bun currently has an annual run rate of $0.
◧◩◪
27. Booris+68[view] [source] [discussion] 2025-12-02 18:55:43
>>Kwpols+s4
They're baking the LORA as we speak, and it'll default to `bun install` too
◧◩◪◨⬒⬓⬔
28. Octoth+79[view] [source] [discussion] 2025-12-02 18:58:58
>>simonw+C7
Oops, thank you :)

regardless, it's certainly not MS.

replies(1): >>stonog+da1
◧◩◪◨⬒⬓
29. vlovic+nd[view] [source] [discussion] 2025-12-02 19:14:25
>>gianca+S4
Server here I used loosely - it obviously runs on any machine (eg if you wanted to deploy an application with it as a runtime). But it’s not useful for web dev itself which was my point.

Frontend work by definitions n doesn’t happen with either Node nor Bun. Some frontend tooling might be using a JS runtime but the value add of that is minimal and a lot of JS tooling is actually being rewritten in Rust for performance anyway.

◧◩◪
30. gkober+Nd[view] [source] [discussion] 2025-12-02 19:16:26
>>singul+I1
I think there's a potential argument to be made that Anthropic isn't trying to make it easier to write TS code, but rather that their goal is a level higher and the average person wouldn't even know what "language" is running it (in the same way most TS devs don't need to care the many layers their TS code is compiled via).
◧◩◪◨⬒
31. LunaSe+ke[view] [source] [discussion] 2025-12-02 19:18:32
>>simonw+97
They could use the Node.js equivalent: https://nodejs.org/api/single-executable-applications.html#s...
replies(2): >>simonw+Ve >>zstscr+jD
◧◩◪◨⬒⬓
32. simonw+Ve[view] [source] [discussion] 2025-12-02 19:21:30
>>LunaSe+ke
They evidently evaluated Node.js in comparison to Bun (and Deno) earlier this year and came to a technical decision about which one worked best for their product.
replies(1): >>dvtkrl+Gs
◧◩◪◨⬒⬓
33. rounce+bf[view] [source] [discussion] 2025-12-02 19:22:48
>>gianca+S4
They could do that already, nothing in the license prohibited them from doing so.
replies(1): >>gianca+Ak
◧◩◪◨⬒⬓⬔
34. gianca+Ak[view] [source] [discussion] 2025-12-02 19:43:08
>>rounce+bf
Sure, but Bun was funded by VCs and needed to figure out how to monetize, what Anthropic did is ensure it is maintained and now they have fresh talent to improve Claude Code.
◧◩
35. throwa+9n[view] [source] [discussion] 2025-12-02 19:54:53
>>sankal+T
No, just that people who borrowed bun 7 million dollars want some of it back...
◧◩◪◨⬒⬓⬔
36. dvtkrl+Gs[view] [source] [discussion] 2025-12-02 20:19:53
>>simonw+Ve
I highly doubt that the JS ecosystem is driven mostly by hype so I highly doubt the nodejs solution even put on a table in an internal issue tracker.
replies(1): >>simonw+Jt
37. logsr+ht[view] [source] 2025-12-02 20:23:38
>>jjorda+(OP)
Claude Code running on Bun is an obvious justification, but Buns features (high performance runtime, fast starts, native TS) are also important for training and inference. For instance, in inference you develop a logical model in code that maps to a reasoning sequence, and then execute the code to validate and refine the model, then use this to inform further reasoning. Bun, which is highly integrated and highly focused on performance, is an ideal fit for this. Having Bun in house means that you can use the feedback from all of automation driven execution of Bun to drive improvements to its core.
◧◩◪◨⬒⬓⬔⧯
38. simonw+Jt[view] [source] [discussion] 2025-12-02 20:24:52
>>dvtkrl+Gs
Claude Code shipped on top of Node.js for the first four months of its existence.

Why wouldn't they consider their options for bundling that version into a single binary using Node.js tooling before adopting Bun?

◧◩◪◨⬒⬓
39. zstscr+jD[view] [source] [discussion] 2025-12-02 21:12:37
>>LunaSe+ke
Every time I see people mention things like this in node vs bun or deno conversations I wonder if they even tried them.

>The single executable application feature currently only supports running a single embedded script using the CommonJS module system.

>Users can include assets by adding a key-path dictionary to the configuration as the assets field. At build time, Node.js would read the assets from the specified paths and bundle them into the preparation blob. In the generated executable, users can retrieve the assets using the sea.getAsset() and sea.getAssetAsBlob() APIs.

Meanwhile, here's all I need to do to get an exe out of my project right now with, assets and all:

> bun build ./bin/start.ts --compile --outfile dist/myprogram.exe

> [32ms] bundle 60 modules

> [439ms] compile dist/myprogram.exe

it detects my dynamic imports of jsons assets (language files, default configuration) and bundles them accordingly in the executable. I don't need a separate file to declare assets, declare imports, or do anything other than just run this command line. I don't need to look at the various bundlers and find one that works fine with my CLI tool and converts its ESM/TypeScript to CJS, Bun just knows what to do.

Node is death through thousand cuts compared to the various experiences offered by Bun.

Node adds quite the startup latency over Bun too and is just not too pleasant for making CLI scripts.

replies(1): >>heldri+aW
◧◩◪◨⬒⬓⬔
40. heldri+aW[view] [source] [discussion] 2025-12-02 22:59:11
>>zstscr+jD
I agree, they seem to have never tried it at all! Bun DX is the best, and Bun is the trend setter. Others are just catching up!
replies(1): >>LunaSe+bJ3
◧◩◪◨⬒⬓⬔⧯
41. stonog+da1[view] [source] [discussion] 2025-12-03 00:53:02
>>Octoth+79
Microsoft owns npm outright and controls every aspect of the infrastructure that node.js relies on. It also sits on the board (and is one of the few platinum members) of the Linux Foundation, which controls openjs. It is certainly MS.
◧◩◪◨
42. dangoo+8x1[view] [source] [discussion] 2025-12-03 04:47:02
>>re-thc+x2
except for losing money?
◧◩◪◨⬒⬓⬔⧯
43. LunaSe+bJ3[view] [source] [discussion] 2025-12-03 19:28:25
>>heldri+aW
Yeah, just switch to a non-NPM compatible and inexistant ecosystem just because you need to specify a few parameters in a config.

Anthropic is trying to IPO at a valuation of $300B so if their engineers nor their AI can be bothered to do this then maybe they're not as good as they think they are.

replies(1): >>zstscr+vW4
◧◩◪◨⬒⬓⬔⧯▣
44. zstscr+vW4[view] [source] [discussion] 2025-12-04 03:31:25
>>LunaSe+bJ3
>Yeah, just switch to a non-NPM compatible and inexistant ecosystem just because you need to specify a few parameters in a config.

Yeah.. you do not know what you are talking about.

I run my test suites on both node and bun because I prefer to maintain compatibility with node and it works just fine. I use some of bun's APIs, like stringWidth and have a polyfill module that detects if it's not bun and loads an alternative library through a dynamic import.

Not NPM compatible? Bun is literally a drop in for NPM, in fact you could use it solely as a replacement for NPM and only use node for actual execution if that's your thing. It's much faster to run bun install than npm install and it uses less disk space if you have many projects.

The developer experience on bun is so much better it isn't funny. It remains prudent, I would agree, to not depend too heavily on it, but Bun is many things: a runtime, a set of additional APIs, a replacement for the dogslow npm, a bundler etc. Pick the parts that are easily discarded if you fear Bun's gonna go away, and when using their APIs for their better performance write polyfills.

>Anthropic is trying to IPO at a valuation of $300B so if their engineers nor their AI can be bothered to do this then maybe they're not as good as they think they are.

Or maybe you should have a cold hard look in front of the mirror first and think twice before opening your mouth because the more you write the more the ignorance is shown.

[go to top]