Go vs. Rust? Choose Go
Much as I like Rust, I have to agree.  When you have to get it done, use Go. When you want to explore advanced experimental programming constructs, use Rust. The Go guys knew when to stop. Arguably they stopped too early, before generics or parameterized types, and &quot;interface[]&quot; is used too much. But that doesn&#x27;t seem to be a big overhead item.<p>Rust has the complexity of C++ plus additional complexity from the functional community.  Plus lots of fancy template cruft.<p>The trouble with language extensibility is that people use it without an overall plan. The end result is a Winchester Mystery House language.[1]  LISP went down this rathole, and Scheme had to be developed to get out of it.  C++ went that way when nobody stopped the Boost crowd before it was too late.  Now it&#x27;s happening to Rust.<p>(Anyone involved in language design should see Václav Havel&#x27;s &quot;The Memorandum&quot;.  Or at least read it; I&#x27;ve seen it performed, but it&#x27;s not performed often.)<p>[1] <a href="http:&#x2F;&#x2F;www.winchestermysteryhouse.com&#x2F;" rel="nofollow">http:&#x2F;&#x2F;www.winchestermysteryhouse.com&#x2F;</a>