<i>&gt; The Andrei guy says that Rust places too much emphasis on &quot;clerical&quot; memory management. This is not like a person who learned PHP from a couple w3schools article deciding that Lisp is &quot;weird&quot;. The criticism is not that Rust is &quot;weird&quot; or somehow unintelligible, it&#x27;s a direct critique of the language designers&#x27; choices.</i><p>It might be a direct critique, but it&#x27;s a critique of an incomplete picture of Rust: the rules that allow Rust to avoid a GC offer benefits far beyond just that, such as being a core component of Rust&#x27;s concurrency story[1], and avoiding problems such as iterator invalidation (not generally a memory safety problem in a GC&#x27;d language, but still a semantic one, e.g. Java&#x27;s ConcurrentModificationException).<p>(The &quot;Weird feature #3&quot; part of the article is exactly this point, although I think it doesn&#x27;t go far enough in calling out the incomplete picture of Rust implied by the original quote.)<p>[1]: <a href="http:&#x2F;&#x2F;blog.rust-lang.org&#x2F;2015&#x2F;04&#x2F;10&#x2F;Fearless-Concurrency.html" rel="nofollow">http:&#x2F;&#x2F;blog.rust-lang.org&#x2F;2015&#x2F;04&#x2F;10&#x2F;Fearless-Concurrency.ht...</a>