<p><pre><code>  &gt; Rust programs consume so much resources that it could 
  &gt; just use a GC
</code></pre>
I&#x27;m not sure where this is coming from. Everyone that I&#x27;ve spoken to about using Rust in place of managed languages has noted incredible reductions in memory usage. Indeed, this was one of the primary reasons for Dropbox adopting Rust for their core storage engine. Quoting from <a href="https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=11283688" rel="nofollow">https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=11283688</a> :<p><i>&quot;The reasons for using rust were many, but memory was one of them. Primarily, for this particular project, the heap size is the issue. One of the games in this project is optimizing how little memory and compute you can use to manage 1GB (or 1PB) of data. We utilize lots of tricks like perfect hash tables, extensive bit-packing, etc. Lots of odd, custom, inline and cache-friendly data structures. We also keeps lots of things on the stack when we can to take pressure off the VM system. We do some lockfree object pooling stuff for big byte vectors, which are common allocations in a block storage system. It&#x27;s much easier to do these particular kinds of optimizations using C++ or Rust.&quot;</i><p>And the above paragraph is using Go as a baseline, which itself already tends to use less memory than Java.