Please Do Not Vibe Fuck Up This Software

Re:Please Do Not Vibe Fuck Up This Software – Rsync by Matl on Sunday May 31, 2026 @06:15AM (#48344474)

You're conflating why people want to rewrite it in Rust vs what is the likely end result i.e. I do think people want to rewrite things in Rust because they believe long-term it will mean fewer (memory safety etc.) bugs especially because there's been almost no meaningful improvement in this space for a long time. But of course in the short term it will mean regressions compared to the established C written version.

That is different from AI where the calculus seems to be that if AI isn't involved, it aien't relevant.

[ Parent | on HN ]

Re:Please Do Not Vibe Fuck Up This Software – Rsync by lelanthran on Sunday May 31, 2026 @07:01AM (#48344727)

> I do think people want to rewrite things in Rust because they believe long-term it will mean fewer (memory safety etc.) bugs

I don't believe that anymore - if that were true, the large portion of code now being rewritten in Rust wouldn't be vibe-coded slop.

I'd be more willing to believe that "quality" was the reason if those doing the rewrite weren't fucking vibing everything!

[ Parent | on HN ]

Re:Please Do Not Vibe Fuck Up This Software – Rsync by Matl on Sunday May 31, 2026 @07:07AM (#48344774)

> if that were true, the large portion of code now being rewritten in Rust wouldn't be vibe-coded slop.

There may be some recency bias with the whole Bun fiasco, but Bun is after all owned by Anthorpic.

The wast majority of software in Rust that's actually used is not vibe coded as far as I know. There may be a large number of vibe coded Rust projects on GitHub but that's a poor metric to judge by given how easy it is to publish a new repo.

Is a large portion of in use Rust code vibecoded? I don't believe so.

[ Parent | on HN ]