Top
Best
New

Posted by Chaoses 3 hours ago

Rewrite Bun in Rust has been merged(github.com)
94 points | 85 commentspage 2
sensanaty 1 hour ago|
Love seeing the tests themselves getting modified, with random `sleep(1)` thrown around in a few of them. This bodes well, I pray some idiot at some large AI co actually ends up using this garbage in prod
nDRDY 1 hour ago||
Why didn't they ask Claude to remove all of the `unsafe` at the same time??
bharxhav 1 hour ago||
This canary will never leave the mine. (unless Anthropic opens their wallet again)
perching_aix 1 hour ago||
PR so thick, the page failed to load the first time I opened it, and the comments still continue to fail to load. Absolutely hilarious. Though that may be just GitHub having a normal one, hard to tell these days.

1 009 257 lines added

4024 lines removed

6755 commits

2188 files touched

I haven't the slightest clue how anyone would even remotely hope to review this. I guess by just using even more AI? Or maybe by throwing some über hardcore lint pass onto it? It really seems like more an exercise in risk assessment than code review.

chrysoprace 39 minutes ago|
Not sure there is much of a point in reviewing a port of this size. It has >1000 instances of `unsafe` and uses the same patterns as the zig code according to Jarred. It feels like a vibe-ported version of what the TypeScript team are doing porting from TypeScript > Go with codemods.
q3k 1 hour ago||

  $ grep --exclude-dir=.git -r 'unsafe {' | wc -l
  10465
Nice.
K0nserv 59 minutes ago||
It's not that weird to end up with this when translating C/Zig/C++ to Rust. A first pass can use unsafe and then when the code is in Rust you can work on reducing the unsafe.

Trying to eliminate all unsafe as part of the rewrite, whether done by human or LLM, would be making too big of a change in the process of rewriting.

q3k 55 minutes ago||
> would be making too big of a change in the process of rewriting

God forbid the already unreviewable -710kloc/+1mloc change get any bigger!

K0nserv 52 minutes ago||
Sure, but that's kind of orthogonal. Imagine doing this by hand I still think going like-for-like with the Zig, even if that means a lot of unsafe, is a good approach.

But I suppose if you are already using LLMs it's more reasonable to try and go from Zig straight to Rust with no/minimal unsafe.

janice1999 1 hour ago||
The benefit of using Rust is that you know exactly where the unsafe code is so you can handle it explicitly and deliberately to avoid issues by imposing carefully crafted constraints... oh.
classicposter 1 hour ago||
It's interesting that the developer who spearheaded the hype of Zig abandoned the engineering without addressing the segfault. They could have also taken the approach of gradually porting from Zig to Rust via FFI. Yes, this is a slop show by the AI lab.
ptrl600 1 hour ago||
Hey, it forgot to change the README!
feverzsj 1 hour ago||
How they gonna do refactoring, bugfix or other maintenance on generated code? Ask LLM?
pixel_popping 1 hour ago|
Yes, only LLMs from now on.
wateralien 1 hour ago||
Deno's approach from the beginning seems to have proven out.
ninjahawk1 1 hour ago|
“+1,000,000” changes in a single commit is insane.
ahepp 1 hour ago||
The really interesting thing to do would be to ask the agents to submit the diff as a coherent patchset...
dluan 1 hour ago|||
> "The codebase is otherwise largely the same. The same architecture, the same data structures."
ihateolives 1 hour ago||
Ship of Theseus.
paulddraper 1 hour ago||
And 6700 commits.
eqvinox 1 hour ago||
No wonder GitHub is down

/s

More comments...