Rust vs. Go
From ESR&#x27;s conclusion is this:<p>&gt; For comparison, I switched from Rust to Go and, in the same amount of time I had spent stuggling [sic] to make even a &lt;100 LOC partial implementation work, was able to write and test the entire exterior of an IRC server - all the socket-fu and concurrency handling - leaving only the IRC-protocol state machine to be done.<p>I don&#x27;t think this is an unusual experience. I&#x27;d consider myself a journeyman programmer with 16 years of experience and probably a dozen languages under my belt. Learning Go was unique: after 3 days I felt productive; After 2 weeks I sort of looked around and said &quot;is this it?&quot; Go gets out of your way for the most part, and performs as advertised.<p>For a lot of programmers, for a lot of projects, that&#x27;s exactly what you want.<p>I&#x27;ve attempted to learn Rust a few times, and it always feel like I&#x27;m moving uphill.<p>Rust is awesome for a number of problem spaces, so I&#x27;m not knocking it. And Go _isn&#x27;t_ awesome in a lot of ways (vendoring, I&#x27;m looking at you). But it feels like there are a lot of core, language-level things Rust needs to improve to attract more non-genius developers.