<story><title>Evaluation of C, Go, and Rust in the HPC environment [pdf]</title><url>http://octarineparrot.com/assets/mrfloya-thesis-ba.pdf</url></story><parent_chain></parent_chain><comment><author>bsdetector</author><text>The author has a &amp;quot;lack of equal experience in the three evaluated languages&amp;quot;, especially C, but is comparing them for development time and SLOC based on a sample size of one developer and one very small program.&lt;p&gt;He rewrites a distributed program as a threaded one, because Rust and Go didn&amp;#x27;t have a distributed computing library, but says Go and Rust have &amp;quot;similar performance&amp;quot; in HPC.&lt;p&gt;He says he was surprised at the C performance, but there&amp;#x27;s no investigation of a cause.  Maybe just because C is slow...&lt;p&gt;I don&amp;#x27;t mean to be overly critical, but these results in the paper mean absolutely nothing.  It&amp;#x27;s a waste of time.</text></comment>
<story><title>Evaluation of C, Go, and Rust in the HPC environment [pdf]</title><url>http://octarineparrot.com/assets/mrfloya-thesis-ba.pdf</url></story><parent_chain></parent_chain><comment><author>dgacmu</author><text>The problem with reading this in BS thesis form is that it hasn&amp;#x27;t gone through the wringer enough.  Most of the performance comparison results vs C are bogus because (to its credit, as noted), the author accidentally compiled some important support libraries for the C version &lt;i&gt;without optimization&lt;/i&gt; and used those on the cluster.  Oopsie.&lt;p&gt;&lt;i&gt;As briefly mentioned in the previous chapter this performance regression might have been caused by the two unoptimized libraries that were compiled on the development laptop and copied to the cluster.&lt;/i&gt;</text></comment>