And this will probably give rust a bad name if most of the code is horrid vibe coded stuff. (Cuck coded?)
Evotech@lemmy.world 2 days ago
Vibe coded i guess?
TBi@lemmy.world 2 days ago
faercol@lemmy.blahaj.zone 1 day ago
Hmmmm, the first blog posts about rewriting the backend part from Go to Rust are a few years old by now (early 2020) so it’s clearly not a “let’s vibecode everything in two weeks” kind of project.
However… The later stages are probably vibecoded… Yeah, that would check out today.
entwine@programming.dev 2 days ago
99% of new Rust projects today are vibe coded, so probably yeah
nightlily@leminal.space 2 days ago
I get why vibe coders love Rust - it’s a lot harder to shoot yourself in the foot if rustc is checking your lifetimes, but holy shit is the code I’ve seen from them the most unholy mess. Rust is difficult enough to read at the best of times but LLMs don’t even bother with any kind of module structure. Just thousands of lines of vomit in single files and a worrying amount of
unsafe.Fiery@lemmy.dbzer0.com 1 day ago
Just tell the clanker to use modern practices poof fixed.
Jokes aside a lot of that bad code can be detected by static linting tools and gated on, making it impossible for any of those to reach main.
boonhet@lemmy.zip 2 days ago
Honestly sounds like LLMs have learned that from half the rust projects I’d seen before the LLM craze lol
FukOui@lemmy.zip 1 day ago
Unsafe? For vibe coded client/ backend?