this post was submitted on 13 Jul 2026
71 points (96.1% liked)
Programming
27697 readers
236 users here now
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Rules
- Follow the programming.dev instance rules
- Keep content related to programming in some way
- If you're posting long videos try to add in some form of tldr for those who don't want to watch videos
Wormhole
Follow the wormhole through a path of communities !webdev@programming.dev
founded 3 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Zig is not as strict as Rust for memory management
Unsafe rust too
yes, but when you make a port from one language to another, usually you want to rewrite it as a translation first, then refactor later with the features that language provides. A port that refactors everything in the first release is too risky.
The fact the translation has unsafe blocks only demonstrates the Zig version is not really safe as per Rust standards.
my comment was just pointing out to unsafe rust blocks used in sloppy rewrite.
You clearly don't even know what
unsafein rust means. And it's not something you can avoid when FFI is involved, slopping involved or otherwise.I see what you're saying, but there's no need to be rude.
Claude is it you?
😇
I do love me some internet gantry commentary. Especially when it's super confident and acting knowledgable, with multiple layers of genius on display.
where is quote from? You pretend this is a quote of something I wrote?