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

[–] [email protected] 17 points 4 months ago (5 children)

a kernel module should not be written in Go

[–] 5C5C5C 4 points 4 months ago (4 children)

Rust makes sense though.

[–] technom 8 points 4 months ago (1 children)

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.

[–] [email protected] 2 points 4 months ago

Well, modern c++ with smartpointers is quite good IMO.

C on the ither hand is like swimming with sharks, with a nosebleed.

load more comments (2 replies)