<story><title>Why Discord is switching from Go to Rust (2020)</title><url>https://blog.discord.com/why-discord-is-switching-from-go-to-rust-a190bbca2b1f</url></story><parent_chain><item><author>jjjeii3</author><text>GO promised to be very fast, but if you check the actual benchmarks:&lt;p&gt;&lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;www.techempower.com&amp;#x2F;benchmarks&amp;#x2F;#section=test&amp;amp;runid=8ca46892-e46c-4088-9443-05722ad6f7fb&amp;amp;hw=ph&amp;amp;test=plaintext&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;www.techempower.com&amp;#x2F;benchmarks&amp;#x2F;#section=test&amp;amp;runid=8...&lt;/a&gt;&lt;p&gt;High-level C# (asp.net) is almost twice as fast as GO in the benchmark... Rust is also in the top 3.&lt;p&gt;So, why should I use GO instead of C#, if ASP.NET&amp;#x2F;C# is so blazing fast and requires a lot less lines of code to achieve the same? -&amp;gt; It makes absolutely sense to switch to C# or Rust.</text></item></parent_chain><comment><author>Shadonototro</author><text>Don&amp;#x27;t look at that kind of benchmark, most cheat, and notice how latency is bad, because C# is not native code, so the JIT needs warmup just like java, wich introduces hicups and non-deterministic performance&lt;p&gt;So these perfect situations where you only do the same thing and call same code over and over never happen; never!&lt;p&gt;Anyways, GO isn&amp;#x27;t popular for its RAW perf, GO is popular because:&lt;p&gt;- Simple language&lt;p&gt;- Native code&lt;p&gt;- GC&lt;p&gt;- Cross compilation&lt;p&gt;- Fast iteration (build&amp;#x2F;rebuild&amp;#x2F;deploy)&lt;p&gt;- Relatively tiny, statically compiled executable</text></comment>
<story><title>Why Discord is switching from Go to Rust (2020)</title><url>https://blog.discord.com/why-discord-is-switching-from-go-to-rust-a190bbca2b1f</url></story><parent_chain><item><author>jjjeii3</author><text>GO promised to be very fast, but if you check the actual benchmarks:&lt;p&gt;&lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;www.techempower.com&amp;#x2F;benchmarks&amp;#x2F;#section=test&amp;amp;runid=8ca46892-e46c-4088-9443-05722ad6f7fb&amp;amp;hw=ph&amp;amp;test=plaintext&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;www.techempower.com&amp;#x2F;benchmarks&amp;#x2F;#section=test&amp;amp;runid=8...&lt;/a&gt;&lt;p&gt;High-level C# (asp.net) is almost twice as fast as GO in the benchmark... Rust is also in the top 3.&lt;p&gt;So, why should I use GO instead of C#, if ASP.NET&amp;#x2F;C# is so blazing fast and requires a lot less lines of code to achieve the same? -&amp;gt; It makes absolutely sense to switch to C# or Rust.</text></item></parent_chain><comment><author>d1str0</author><text>Performance is rarely the top priority for a software engineering project. If you task a whole team to switch from Go to Rust or C# purely because “Rust goes brrr” you’re going to have a bad time.&lt;p&gt;I use Go because its decently fast, I like the syntax, has a great stdlib, and I feel like it’s very easy to share a Go codebase with other engineers.</text></comment>