3 ms·
Java may be memory safe but it is not data race safe (unlike Rust, the compiler does not enforce cross-thread synchronization). So there is still a safety-relat
by School-Cotton 2y ago
Java may be memory safe but it is not data race safe (unlike Rust, the compiler does not enforce cross-thread synchronization). So there is still a safety-related reason to use Rust over Java.
That said, I don't really think Rust is a good choice for CRUD apps, because development velocity is more important than performance and they probably don't need to be multithreaded anyway.
But Rust would have been great for a lot of "systems" stuff that was historically written in Java, like Flink or Hadoop for example.
- tptacek 2y agoI feel like I've had this debate many, many times, and it always ends in the same place: I'm willing to concede that there are a subset of correctness/reliability bugs that Rust's error handling and type system mitigate, but not that any of those bugs are material to security, which is what most people are talking about when the discussion turns to memory safety. And, of course, Rust admits concurrency bugs too! We just ran into a huge one.
- School-Cotton 2y agoI didn’t think we were having a debate. You insinuated that Rust isn’t ideal for CRUD apps, and I agreed with you.
- tptacek 2y ago"Debate" was too confrontational a word, sorry about that.