And in absolute terms?
In contrast, memory-unsafe languages don't even try to have a TCB relative to which memory safety is specified. That's the main difference.
It's not like Java is immune to memory safety-related implementation bugs either (e.g., [0]):
> A resource area allocated object is probably passed/used outside of the scope of the corresponding ResourceMark (similar to JDK-8325672).
So "blows Rust away in memory safety" doesn't seem quite supported enough?
it has been discussed bilion times