this post was submitted on 26 Jan 2024
85 points (92.1% liked)
Programming
17366 readers
178 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 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Except that actually doing anything with hardware is "unsafe."
Well, yeah, because doing things with hardware is just always unsafe in that sense, no matter if you're implementing it in Rust or C or Assembly. As long as you know what you're doing (and the hardware manufacturer did, too), it's not actually unsafe.
Rust just decided to isolate the code parts where you need to be extra smart like that, whereas in C or Assembly, you might need to be extra smart throughout the entire code base.
Obviously, no sane C programmer would just randomly start scrubbing memory addresses in UI code, but it's still just helpful to have the naughty code clearly indicated.
Hardware is inherently unsafe.