this post was submitted on 31 Aug 2023
68 points (97.2% liked)
Programming
17479 readers
320 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 [email protected]
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
idk if youve heard but its memory safe
I’d have to be living under a particularly large rock to be unaware of that. “It’s memory safe” isn’t that big of a deal to me. Even building concurrent systems, memory safety has never been a significant issue for me with Go.
i think go is also considered memory safe due to the garbage collector
Go is memory safe due to its garbage collection. Which adds a decent overhead generally.
Rusts memory safety is enforced at compile time and therefore has zero cost at runtime.
For a system level language this can be really important.
In my book, "memory safety" also means avoiding data races. AFAIK Rust prevents most or all races by enforcing ownership and lifetime of pointers.