Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Bun's unreleased Rust port has 13,365 unsafe blocks

bun.com

Post reply on HN
Print view View original

1–10 of 57 posts

Re: Bun's unreleased Rust port has 13,365 unsafe blocks

#2

Post by evil-olive »

right at the very top:

> Bun · Rust codebase audit · May 21, 2026 · AI generated

nice of them to be up-front about it, I guess.

the port is AI slop, littered with 13k unsafe blocks.

and this blog post is more AI slop, claiming to present a "plan" for how to reduce that number.

why should anyone trust anything they output? all they're trying to do is cover up their slop with more slop.

if you're cleaning your house, and the dirt can't all fit under one rug, the obvious solution is to buy another rug.

Re: Bun's unreleased Rust port has 13,365 unsafe blocks

#3

Post by jarym »

evil-olive wrote: post #2

right at the very top: > Bun · Rust codebase audit · May 21, 2026 · AI generated nice of them to be up-front about it, I guess. the port is AI slop, littered with 13k unsafe blocks. and this blog post is more AI slop, claiming to present a "plan" for how to reduce that number. why should anyone trust anything they output? all they're trying to do is cover up their slop with more slop. if you're cleaning your house, a…

Dunno, AI was quick to prove it could be done. I’ve found while it’s initial attempts might be slop, with good direction it can really tidy things up

Re: Bun's unreleased Rust port has 13,365 unsafe blocks

#4

Post by maipen »

evil-olive wrote: post #2

right at the very top: > Bun · Rust codebase audit · May 21, 2026 · AI generated nice of them to be up-front about it, I guess. the port is AI slop, littered with 13k unsafe blocks. and this blog post is more AI slop, claiming to present a "plan" for how to reduce that number. why should anyone trust anything they output? all they're trying to do is cover up their slop with more slop. if you're cleaning your house, a…

I trust them because of their reputation. I have been a bun user before v1.0.0 and I experienced some shortcomings, bugs, memory leaks and things of that nature. But all of them were eventually patched, and it has become my go to runtime for at least 2 years now.

I trust their judgement to do the right thing.

I don’t understand the overreaction since this is a parallel development.

If it turns out to be better than make it default. Bugs get fixed it’s not like their zig version didn’t have issues before.

Re: Bun's unreleased Rust port has 13,365 unsafe blocks

#6

Post by pdpi »

evil-olive wrote: post #2

right at the very top: > Bun · Rust codebase audit · May 21, 2026 · AI generated nice of them to be up-front about it, I guess. the port is AI slop, littered with 13k unsafe blocks. and this blog post is more AI slop, claiming to present a "plan" for how to reduce that number. why should anyone trust anything they output? all they're trying to do is cover up their slop with more slop. if you're cleaning your house, a…

Let's save the accusations of sweeping things under the rug for if and when they actually release this rewrite in a sloppy, buggy state.

Re: Bun's unreleased Rust port has 13,365 unsafe blocks

#8

Post by fdsajfkldsfklds »

firtoz wrote: post #5

> Bun's Rust port has not shipped in a released build yet. The Bun you install today still runs the original Zig implementation. This audit is the pre-release pass over the port. That's good to see. I was getting a bit worried but now feeling better about it.

I am looking forward to the first release tomorrow though!
Post reply on HN