| ▲ | aja12 an hour ago | |||||||||||||
It's important to note that Java, like Rust, is generally seen as a memory safe language. But it has bits of assembly, just like Rust has unsafe blocks, to handle some operations. Hence the Java2shell recent vulnerability. Granted Rust may have less need for them and more facilities to audit them, but it is not by itself a panacea that will fix all memory issues. In essence, there is no software stack that is fully memory safe, it is more a matter of restricting the memory unsafe parts in fewer, more scrutinized, better contained sections. | ||||||||||||||
| ▲ | zamadatix an hour ago | parent | next [-] | |||||||||||||
Yeah, "memory safe" goes out the window if you prefer to implement parts in assembly. This is where portable SIMD (e.g. the Java vuln was from SIMD), which is abstracted & safe but not necessarily as performant as it could be, is becoming a more reasonable trade off. Of course I'm not sure how much it counts to be "using a memory safe language" when you have to call put to unsafe code anyways. I.e. just because the library you'd like to use is C but the rest of your project is Rust doesn't mean you're really using a me ory safe language, it means you're sometimes using one. We have a long way to go before environments allow using memory safety fully I think. | ||||||||||||||
| ▲ | ninkendo 35 minutes ago | parent | prev | next [-] | |||||||||||||
OP didn’t say anything about Rust, by the way. This post comes off as being defensive about a point nobody made. | ||||||||||||||
| ▲ | anthk 42 minutes ago | parent | prev [-] | |||||||||||||
Rust it's far better than Java. Since the old times Java was seen as a CVE generating machine for GNU/Linux environments. | ||||||||||||||
| ||||||||||||||