this post was submitted on 20 Jul 2024
422 points (98.0% liked)
Programmer Humor
19176 readers
952 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
- Keep content in english
- No advertisements
- Posts must be related to programming or programmer topics
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
Much less invest in a memory safe language. If they don't take a serious look at Rust, Go, or some other memory-safe language... I'll stop right there: they won't. Management doesn't give a fuck as long as the cost is within manageable margins, or they can fire a bunch of scapegoats but change nothing.
Anti Commercial-AI license
a kernel module should not be written in Go
Rust makes sense though.
I don't think that rust would have prevented this one, since this isn't a compile time error (for the code loader).The address dereferencing would have been inside an unsafe block. What was missing was a validity check of the CI build artifacts and payload check on the client side.
I do however, think that the 'fingers-crossed' approach to memory safety in C and C++ must stop. Rust is a great fit for this use case.
Well, modern c++ with smartpointers is quite good IMO.
C on the ither hand is like swimming with sharks, with a nosebleed.