Bun Rust rewrite: "codebase fails basic miri checks, allows for UB in safe rust"

Post by fyrn_ » Sat, May 16, 2026, 4:18 PM UTC

nicce wrote: post #297

gorjusborg wrote: post #229

Here's the thing: I was first interested in Bun because it was written in Zig. I was interested in Zig because I respected Andrew Kelley's decision-making, and his taste matched my own. I got really excited about Bun for many reasons after that, but they essentially came down to a similar root: the decisions were ones that I respected and would probably have made myself if I had thought of them. I was a little concer…

Bun is really interesting project, but the amount of segmentation faults in issues was too concerning for serious production usage. I guess this is one direction to fix it, but let’s see.

Post by whateveracct » Sat, May 16, 2026, 4:22 PM UTC

dang wrote: post #322

whateveracct wrote: post #236

Earlier quoted context omitted.

looking at my recent comment history, this was the only comment i see that qualifies https://news.ycombinator.com/item?id=48136130

I was thinking of https://news.ycombinator.com/item?id=48152395 . If I hadn't seen that one, I probably wouldn't have interpreted the GP this way.

Post by veidr » Sat, May 16, 2026, 4:41 PM UTC

coldtea wrote: post #328

veidr wrote: post #315

Earlier quoted context omitted.

I can understand where you are coming from, but I myself am coming from a quite different place. I'm a long-time Deno fan, and to me Bun was less interesting because a.) it seemed like a much-less-ambitious Deno, and b.) I don't want to learn Zig, so I wasn't likely to try to hack on Bun itself, even just recreationally. But, I warmed up to Bun over the last couple years almost against my own will — trying to maintai…

> and to me Bun was less interesting because a.) it seemed like a much-less-ambitious Deno I don't know, I've followed Deno, and it appeared to me an incredibly low ambition from the get go.

Post by coldtea » Sat, May 16, 2026, 6:03 PM UTC

veidr wrote: post #335

coldtea wrote: post #328

Earlier quoted context omitted.

> and to me Bun was less interesting because a.) it seemed like a much-less-ambitious Deno I don't know, I've followed Deno, and it appeared to me an incredibly low ambition from the get go.

lol — what you're saying doesn't make sense to me, but I'm sure it makes sense to somebody What I was specifically referring to is Deno (originally) trying to fix the (glaring, fundamental) problems that Node imposes on the world, vs just do them faster.

Post by ok_dad » Sat, May 16, 2026, 6:05 PM UTC

quectophoton wrote: post #294

mort96 wrote: post #288

Earlier quoted context omitted.

The core issue is philosophical. Whether you happen to have public infrastructure which provides a web front-end for your git repository, and what exact server that web front-end happens to be hosted on, ought to be completely incidental to compiling source code. But since you ask, Go is the best example of how this can go terribly wrong in practice, IMO. Here are just a few scattered pain points I've encountered: *…

Don't forget: * No relative imports. * The `require` directives from the `go.mod` files of your dependencies are always ignored. Those two combined, mean that there's no easy way to fork a dependency. It's doable, but some of the maintenance overhead could have been avoided. We don't even get a `go mod tidy` flag that lets us say, "yes, I understand the risks, just copy any `replace` directives that you find in my de…