Taming Go’s memory usage, or how we avoided rewriting our client in Rust
Bit confused by this part of the article:<p>> PRO-REWRITE: Rust has manual memory management, so we would avoid the problem of having to wrestle with a garbage collector because we would just deallocate unused memory ourselves, or more carefully be able to engineer the response to increased load.<p>> ANTI-REWRITE: Rust has manual memory management, which means that whenever we’re writing code we’ll have to take the time to manage memory ourselves.<p>Isn't part of the point of Rust that you <i>don't</i> manage memory yourself, and rather that the compiler is smart enough to manage it for you?