Live data from Hacker News

Rewrite Bun in Rust has been merged

github.com

151–160 of 822 posts

Re: Rewrite Bun in Rust has been merged

#151
post #124

Earlier quoted context omitted.

This is bad for anyone building on Zig.

Why would it be? There is projects like Roc that did the opposite, they went from rust to zig, as they (had to) use lots of unsafe rust. And before you ask, no it was not an AI generated rewrite.

that is the point. rewrite is fine when - you take your sweet time doing that - you still know full well the codebase

that will ensure the new codebase can still be well understood and can continue to grow in foreseeable future

or you can just vibe the whole experience if it is a legacy project with all the specs and edge cases known.

since bun rewrite is neither of the case, it will be a crapfest soon enough.

Re: Rewrite Bun in Rust has been merged

#152
I might not necessarily agree with the haste / stability of this, but I commend Jarred for pushing boundaries on what AI coding is capable of, can't deny that. 4 years ago this would've seemed like science fiction.

Re: Rewrite Bun in Rust has been merged

#153
This will burn the little reputation and trust Bun has been able to achieve in the past couple of years.

I guess this is what happens when you only have to respond to your corporate overlords.

I will migrate my Bun projects in production to something else.

Re: Rewrite Bun in Rust has been merged

#155

Earlier quoted context omitted.

not enough people are emotionally prepared for if it’s not going wrong even in the slightest

Having seen some of the diffs, it's already going wrong in my view.

If most of the glaring problems are addressed (massive unsafe usage), and metrics show improvement (less crashes), then did it really go wrong? The fact the code is not idiomatic is less interesting, because that can be addressed incrementally. Let's wait 3 months and reflect.

Re: Rewrite Bun in Rust has been merged

#156
post #118

We should be greatful for this. This is the one public case study on how large-scale llm-driven code generation actually works out. With node and deno there are reasonable alternatives for everyone who don't want to use bun anymore.

The problem is that many negative effects of this kind of thing won't be clear or immediate, so it's not an easy test to make useful. At minimum, this increases the opacity of the box, reducing perceived trustworthiness.

Re: Rewrite Bun in Rust has been merged

#157
post #71

HN overreacting again. I trust Jarred to make the right decisions regarding bun, which seems to be his passion. Bun has always been amazing since i first tried it, it had some bugs along the way, which didn’t last long. Anything bad that comes from this, will simply be fixed. I hope more software does this and gets rid of their segmentation fault producing code, written in c++ and other unsafe languages I can think o…

It has 10k unsafe blocks, pretty sure those segfaults are still gonna be there

Definitely. That's what a good translation is.

But then, agents can work on removing each unsafe one by one and this will bubble issues.

Re: Rewrite Bun in Rust has been merged

#158
post #18

If this goes wrong even in the slightest , the ridicule about a drug dealer getting high on their own supply will be neverending and grim.

not enough people are emotionally prepared for if it’s not going wrong even in the slightest

However, you can never prove that it hasn't gone wrong, because there are so many long-form problems with software (quiet bugs, maintainability issues, etc). This creates FUD.

Re: Rewrite Bun in Rust has been merged

#159
post #4

Turns out "its just an experiment, you all are overreacting" was just a lie to damp criticism. https://news.ycombinator.com/item?id=48019226

Maybe Anthropic decided to push this because of all the attention the experiment got.

If it works out it’ll be a good study case for marketing.

Post reply on HN