Oh, oh, you don't disagree! The class of memory management bugs caught by the borrow checker only manifest as memory leaks when developing in any boring, garbage-collected memory safe language. Not buffer overflows. Not use after free. None of the excitement advertised on the Rust tin. These things do not occur in boring GC languages. Oh, and in-process data races which must be caught for Rust to be safe at all. Any engineer willing to sacrifice that much productivity based on a theoretical whinge, that is practically treated simply by periodically restarting application nodes, is a total joke. Tolerating memory leaks in high-level development cannot be reasonably extrapolated to "the idea that moving fast is more important than correct and safe code" which is nonsense fearmongering.