FRESH

Hacker News

Home

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

55 points by helloplanets

by avsn

0 subcomment

Wow, this page looks so bad information-wise. There's a trend with such LLM "reporting" of just throwing bunch of numbers, graphs, charts, whatever on the page. Looks impressive from the outside, totally incomprehensible when you try to actually read it.

by 12_throw_away

2 subcomments

Assertions without context, charts about other charts, numbers (so many numbers) without data. An audit with no auditor. Pure infoslop. What a time to be alive.

by amazingamazing

2 subcomments

Could you imagine if Postgres decided to yolo a port (even if unreleased) to rust? Why port the whole thing like this? Why not do it piecemeal and get each piece to prod?
Look no further than their owner for the reason, unless it is merely a coincidence this only happened after a change in ownership…

by mmastrac

0 subcomment

Remember kids, unsafe is not undefined behaviour. It just means you need to prove via unchecked English statements that your code is not UB.

by mariopt

3 subcomments

The current level of insanity with AI is off the charts.
Porting to a safe language without the safety features.

by firtoz

1 subcomments

> 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.

by izietto

2 subcomments

Guys, does anyone know why the decision to port Bun from Zig to Rust? Is it to move to a less niche language?

by evil-olive

3 subcomments

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.

by hmokiguess

1 subcomments

Also, was this done with Mythos or Opus 4.7?

by ryanshrott

0 subcomment

13k unsafe blocks is a reminder that unsafe on its own isn’t the problem, it’s whether that unsafe boundary is small and audited. The number that matters more is how much of the codebase depends on unchecked invariants. If the answer is most of it, the port is moving too fast.

by mpalmer

0 subcomment

I have such contempt for this effort by Anthropic. Jarred has torpedoed so much of the goodwill Bun had earned.

by ponyous

1 subcomments

Bun is(was?) a lot about performance. How does it compare to zig?

by pier25

0 subcomment

This PR piece is only making things worse.

by PufPufPuf

1 subcomments

If you want to dig into Bun's port to Rust, I suggest waiting until they actually release something instead of generating LLM slop charts about unfinished source code.

by kshri24

0 subcomment

Not reading this AI slop.

by nissa-seru

0 subcomment

[flagged]

by hmokiguess

0 subcomment

[dead]