<story><title>Rust Faster</title><url>https://llogiq.github.io/2015/10/03/fast.html</url></story><parent_chain></parent_chain><comment><author>geofft</author><text>Fascinating things I learned from this article:&lt;p&gt;1. The benchmarks game is mostly a game of who can solve the problem fastest with the constraint of &amp;quot;all the code has to be in this language.&amp;quot; It&amp;#x27;s not about how anyone would realistically write the code; if ludicrous optimizations were in-scope for any real-world project, so would be &lt;i&gt;calling out to a different language&lt;/i&gt;. It&amp;#x27;s worse than the usual problem of benchmarks being unrepresentative of real code; the implementations are also unrepresentative.&lt;p&gt;2. Apparently performant Haskell involves unchecked raw memory access? What&amp;#x27;s the story there?</text></comment>
<story><title>Rust Faster</title><url>https://llogiq.github.io/2015/10/03/fast.html</url></story><parent_chain></parent_chain><comment><author>Everlag</author><text>I&amp;#x27;ve been working with rust for about a week now and I&amp;#x27;ve found it a mirror of go in several ways.&lt;p&gt;Go aims to be simple with the aim of being &amp;#x27;easy&amp;#x27; to start writing idiomatically within a few days of jumping into the language. Comparatively, rust is a behemoth in terms of complexity.&lt;p&gt;There&amp;#x27;s the completely relevant compilation speed difference: if rust could compile within 5-10x the time go does, it would be much more pleasant to work with. Being able to compile within 2 seconds on large projects is crazy for iteration speed; having to wait upwards of 10 seconds on toy projects is not.&lt;p&gt;However, rust is stupid fast while also being safer than go. Also, generics; that&amp;#x27;s a flamewar for another day.&lt;p&gt;Context: I&amp;#x27;ve been working with go for around 2-3 years now. I recently decided to pick up rust because of the guarantees it provides along with the crazy performance.</text></comment>