> GCs do various resource clean up that mean certain bugs are not exploitable. Rust does not have that.
All of the work Python does at runtime with a GC, Rust does at compile time with the borrow checker. GC is orthogonal to the idea of memory safety.
> And you didn’t address my second point.
I don't know what you expect. It's a semantically empty statement and thus unfalsifiable. You can flip it around without changing the truth or the meaning:
> you seem to think because you can crash a Rust program that means the memory vulnerabilities of Python are justified.
All of the work Python does at runtime with a GC, Rust does at compile time with the borrow checker. GC is orthogonal to the idea of memory safety.
> And you didn’t address my second point.
I don't know what you expect. It's a semantically empty statement and thus unfalsifiable. You can flip it around without changing the truth or the meaning:
> you seem to think because you can crash a Rust program that means the memory vulnerabilities of Python are justified.