this post was submitted on 12 Aug 2026
171 points (97.2% liked)

Programmer Humor

32763 readers
1018 users here now

Welcome to Programmer Humor!

This is a place where you can post jokes, memes, humor, etc. related to programming!

For sharing awful code theres also Programming Horror.

Rules

founded 3 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] Ghoelian@piefed.social 7 points 17 hours ago* (last edited 17 hours ago) (2 children)

And they're initially doing it without Rust's ~~memory safety~~ borrow checker iirc, so a big part of the benefit isn't there

[–] Traister101@lemmy.today 6 points 15 hours ago

Unsafe Rust code doesn't turn off the borrow checker, it basically just allows you to play with pointers and call code that the compiler can't (or can't right now) statically assert is sound. IE if you roll your own Vtable the functions are safe to call, but the compiler can't tell so you have to use unsafe

[–] mamg22@sh.itjust.works 2 points 15 hours ago* (last edited 12 hours ago)

Ok this is funny. Like "look bro, we rewrote bun in Rust because it's ✨Safe✨ and all that", and they're not even trying lmao

In all seriousness, part of that issue probably comes from the original code already ignoring the safety features of Zig, and whatever LLM they used to port it just doing the most half-assed thing and doing a literal translation of the code.

The future of software development, ladies and gentlemen

Edit: rust safetyYes I know unsafe in rust doesn't mean unsafe code, it just that the compiler trusts you to correctly use the interfaces and references since it won't check them inside such blocks