7 ms·
I wonder if I'm the only one for whom the bun project vanished completely. In software code is only part of the package. Stability and trust are big part of it
by xlii 4mo ago
I wonder if I'm the only one for whom the bun project vanished completely.
In software code is only part of the package. Stability and trust are big part of it, too. And for me 1800 files change PRs created by Anthropic overseen by one person is not necessarily adding to the package.
Even it that'd be the best code and design in the world, I won't use it. I don't trust it.
- monkaiju 4mo agoIm here with ya :)
- sibeliuss 4mo agoThe problem is that you need to twist the cube
- egorfine 4mo agoYeah, I have prepared our company software for migration back to node. I would like to read the promised Jarred's blog post (if it ever comes out) before pulling the plug though.
- afavour 4mo agoI’m amazed folks ever migrated to it at a workplace level TBH. It’s a VC funded runtime, something was always going to happen to it. Node is boring but its governance and ownership is clear.
- tyre 4mo agoWell, it was (is?) significantly easier to use, faster, the team behind it is fantastic, and generally had enough compatibility to run the projects I needed it to. When it’s enough of a drop-in replacement, that’s more than good enough. As long as we’re not adding a hundred bun-specific things, it’s not terribly difficult to back out of, either. Kind of a no-brainer.
- afavour 4mo agoFaster I get. But easier to use?
- egorfine 4mo agoYeah. Take a look at the docs. So much niceties
- hn_throw2025 4mo ago...and now we also have Nub : https://nubjs.com/blog/introducing-nub https://nubjs.com/blog/introducing-nub
- 0x6c6f6c 4mo agoThere is no comparison when running a TypeScript project with Bun vs with Node. Or when mixing ESM and CJS. Or when setting up unit testing. Node and its ecosystem was considerably behind in multiple regards.
- afavour 4mo agoOP said: > it’s not terribly difficult to back out of, either Things like ESM/CJS interop are great but backing out of an ecosystem that uses it is absolutely not trivial. Either it’s a trivial replacement you can drop in with no changes or it’s a notable change you can’t easily switch out. It’s not both.
- kibibu 4mo agoTake a look at Deno. It's pretty great and now has exceptional node compatibility
- re-thc 4mo ago> Take a look at Deno. It's still heavily AI driven. Maybe less than Bun. And they've gone in the route of just taking Node native libraries and what not just because they gave up on working out the compatibility. It's a bit of tacked on mess now.
- kibibu 4mo agoWhere are you seeing that it's heavily AI driven? --- Edit: the contribution guidelines allow AI-assisted patches with disclosure. Also, there are a bunch of recent commits co-authored by bots
- sergiotapia 4mo agomight as well use openclaw at this point. that's the same vibe I'm getting with bun. from engineering excellence and jesus this guy really sweats the details (using zig woah!) to wow this is just openclaw ai permagenerated stuff. not a fan
- okeuro49 4mo agoIt looks like quite a lot of analysis went into the rewrite https://bun.com/bun-unsafe-audit https://bun.com/bun-unsafe-audit If the tests pass, then why not accept the rewrite? An interesting article of Prisma using the rewrite: https://www.prisma.io/blog/bun-rust-rewrite-prisma-compute https://www.prisma.io/blog/bun-rust-rewrite-prisma-compute
- theturtletalks 4mo ago[dead]
- applfanboysbgon 4mo ago> quite a lot of analysis went into the rewrite Literally just prompted for an LLM to review it and asked for a fancy presentation. That is not "quite a lot of analysis". That is anything but. > If the tests pass, then why not accept the rewrite? Because (1) tests passing are absolutely not a guarantee that no regressions were introduced in a change, and (2) even if they were, those tests are the result of thousands of hours of human labour, which is all well and good for the codebase as it currently exists, but who is going to be writing the tests for the 1m loc repo of unread code in the future? Unless you've proven that specifically LLM-generated tests can prevent all possible regressions, you're condemning the future of the project because nobody will be able to continue writing robust tests.
- stbenjam 4mo agoI hear a lot of complaints about bun but nothing concrete about what broke in the migration. You are also assuming one prompt, and then arguing against your assumptions with zero evidence. It is lazy arm chair criticism.
- JCTheDenthog 4mo ago>I hear a lot of complaints about bun but nothing concrete about what broke in the migration. Because it hasn't been released yet (at least not outside of some unstable branches). You can find some criticism of the actual slop here though: https://old.reddit.com/r/rust/comments/1t4033y/buns_rewrite_it_in_rust_branch/ojzuftw/ https://old.reddit.com/r/rust/comments/1t4033y/buns_rewrite_...
- re-thc 4mo ago> And for me 1800 files change PRs created by Anthropic overseen by one person is not necessarily adding to the package. Bun is mostly AI written and AI reviewed at this point (all automated). The 1-person is luxury.
- UqWBcuFx6NV4r 4mo agocitation needed
- solid_fuel 4mo agogo clone the repo and run `git blame`.
- teaearlgraycold 4mo agoFor me it’s still up in the air. I won’t bet against them just yet. Also, did they say only one person reviewed it? I really doubt that. Don’t assume that what you can see on GitHub is the sum of all actions taken.
- camdenreslink 4mo agoYea, more likely for the majority of the code nobody reviewed it. It was over a million line diff.
- NekkoDroid 4mo agoIf we are generous and assume a review speed of 1 line per second, that is still over 11 continuous uninterrupted days of review by a single person.
- fatata123 4mo ago[dead]
- adamddev1 4mo agoEveryone's excited about using AI to make their quick end products. But no-one wants to actually build on or rely on vibe-coded frameworks, languages, or tools.
- maddmann 4mo agoWhat about Claude code?
- deleted 4mo ago[deleted]
- deaddodo 4mo agoI think AI is fine, the problem is what you mentioned: vibe coding. Have AI do work for you, it’s certainly faster in most cases. But just know exactly what it’s generating and building before putting it into production. That’s not some massive bar to surpass.
- lacoolj 4mo agoYeah, but you dont know who is vibe coding and who actually knows the output of what they had LLM make This leads to lack of trust, which the entire open source community is based on. Even if that vibe coded slop is flawless, the stigma will never go away.
- llbbdd 4mo ago
- jhack 4mo ago"Even it that'd be the best code and design in the world, I won't use it. I don't trust it." Nothing about this sentence makes sense. What don't you trust about code you can see and audit yourself? What's untrustworthy about "the best code and design in the world"?
- UqWBcuFx6NV4r 4mo agoI do not agree with OP but to not understand “i don’t have the knowledge and/or resources to audit/review a language port of an entire JS runtime, but I still understand that a big-bang language port is something to be cautious of” is almost wilful tonedeafness
- unknownfuture 4mo agoIt's called "mileage". This new codebase doesn't have any. Who knows what gremlins lurk in some of its darker corners.
- Jarred 4mo ago> new codebase doesn’t have any Claude Code & Prisma use it as of last week.
- marshray 4mo agoThat comment had me reaching for the skull emoji.
- vips7L 4mo agoClaude is riddled with bugs. That doesn’t inspire confidence.
- dijksterhuis 4mo agooriginal comment: >> new codebase doesn’t have any > No longer accurate. As of last week, Claude Code (an incredibly popular CLI tool) runs on Bun’s Rust rewrite.
- cmeacham98 4mo ago
- felooboolooomba 4mo agoAnthropic stuff runs on Bun, that's why they bought it. Should they be careful with Bun? Could Anthropic be a high value target for someone?
- TiredOfLife 4mo agoSo you were fine with AI writing zig code, but AI writing rust is a step too far?
- cavoirom 4mo agoI agree with you. Human is a forgetful race, they just unlearned the zlib lesson. Edit: fixed typos.
- pieter 4mo agoI was willing to gloss over the AI usage because I really like the Bun DX. I used Bun in Shell scripts and small prototypes before and decided to use it for something bigger. But then in a week or so of use, tons of issues appeared. Use-after-free bugs when a client disconnects (both in Zig and the Rust port, funnily enough) which will kill Bun. Unimplemented feature which just return “0” always. Many backpressure bugs which means something like “return new Response(fs.createReadStream(bigFile))” will greedily read and OOM your box. All of these have been reported, robobun has made fixes of various quality, but none of this has been addressed. Some of them have been reported for months. I’d prefer Bun to work on stability rather than fancy features like image processing or threads.
- pjmlp 4mo agoI was already not much interested into it, now even less.
- mi_lk 4mo agoThe entire RIIR saga , not the fact that it's rewritten in a different language, but how the author selectively choose to let certain information surface without clarification, tells you a lot Personally not interested in performative/marketing-driven decision so I am done with the project and the author. Quite disappointed