Live data from Hacker News

I am worried about Bun

wwj.dev

211–220 of 368 posts

Re: I am worried about Bun

#211
I work on Bun, and this post is confusing to me. Me personally and the Bun team continues to dogfood & make Bun better everyday. Our development pace has only gotten faster. Bun's stability has improved significantly since joining Anthropic.

Here are some things shipping in the next version of Bun:

- 17 MB smaller Windows x64 binaries [0]

- 8 MB smaller Linux binaries [1]

- `--no-orphans` CLI flag to recursively kill any lingering processes spawned [3]

- SSL context caching for client TCP & unix sockets, which significantly reduces memory usage for database clients like Mongoose/MongoDB [4]

- Experimental HTTP/3 & HTTP/2 client in fetch [5]

- Experimental HTTP/3 support in Bun.serve() [6]

- Bun.Image, a builtin image processing library [7]

(Along with several reliability improvements to node:fs, Worker, BroadcastChannel, and MessagePort)

The Anthropic acquisition also means Bun no longer needs to become a revenue-generating business. We are very incentivized to make Bun better because Claude Code depends on it, and so many software engineers depend on Claude Code to help get their work done.

[0]: https://github.com/oven-sh/bun/pull/30219

[1]: https://github.com/oven-sh/bun/pull/30098

[2]: https://github.com/oven-sh/WebKit/pull/211

[3]: https://github.com/oven-sh/bun/pull/29930

[4]: https://github.com/oven-sh/bun/pull/29932

[5]: https://github.com/oven-sh/bun/pull/29863

[6]: https://github.com/oven-sh/bun/pull/30032

Re: I am worried about Bun

#213
post #168
post #73

Earlier quoted context omitted.

Why would you want DB drivers and S3 clients in your runtime? That’s exactly what 3rd parties are for, you don’t want to have to update your runtime for a new version of your drivers

And a bug in a dependency you can fix easily. One in the runtime is much harder to fix and you then must compile new versions.

And a supply chain attack is much easier with too many dependencies as well.

Re: I am worried about Bun

#215
TBF, I really haven't done much of anything with Bun other than occasional module testing. I mostly use Deno for my day to day, including a lot of shell scripts the past few years. I liked the newer ergonomics a lot, direct module references in repositories is really nice for shell scripts.

That said, I'm worried about them having good enough monetization while keeping features open... or at least able to be replicated by others. So I can understand some of the concerns.

Re: I am worried about Bun

#216
tl;dr: I have concerns. Not because Bun is bad. Bun is great. It is not bad. But Claude was good. And now it is bad. Bun is owned by Anthropic. Transitive property. Maybe. I hope I’m wrong.

Re: I am worried about Bun

#218

I just spent a couple hours migrating my knife sharpening website backend from Bun to Node. Feels good to avoid that lock-in. I was initially gung-ho for Bun but increasingly unsure about it. Things I'll miss for sure: - Querying sqlite with tagged template literals - Bun.password.verify being argon2 is a better default - HTML imports - JSX transpilation - Auto loading .env file https://burlyburr.com , which hits htt…

Why not just write a small helper library to add back the features you miss? Node includes SQLite and Argon2 at least, if the issue is the interface then that is easily fixed.

Re: I am worried about Bun

#219
post #211

I work on Bun, and this post is confusing to me. Me personally and the Bun team continues to dogfood & make Bun better everyday. Our development pace has only gotten faster. Bun's stability has improved significantly since joining Anthropic. Here are some things shipping in the next version of Bun: - 17 MB smaller Windows x64 binaries [0] - 8 MB smaller Linux binaries [1] - `--no-orphans` CLI flag to recursively kill…

Saying that you “work on Bun” is such a radical understatement. I have my reservations about Anthropic, but I don’t see how Bun could go wrong with you at the helm. And I’m sure that you are putting the stability and funding of a larger organization to good use :)

I’ve been a Bun maximalist since the beginning. Thank you Jarred!!!

Re: I am worried about Bun

#220
post #39

Earlier quoted context omitted.

> 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 partially agree with you, but I also think that it's good that people can make something they want, that seems to have no monetization path, and have some hope of being bailed out. It's not great that the search for profit will usually corrupt projects, but the other most common option is that the projects don't exist at all. It's very rare (or it used to be before this year) that someone can do something like this…

I'm with you... I think it's helped Node.js a lot to have Bun and Deno implementing new features that help push node forward. I think it's been a bit of a miss not integrating npm into node along the way... Mostly in that npm is a separate org from node, which is its' own issue... I kind of like JSR a lot myself, so hope it continues to pick up some traction.
Post reply on HN