Before getting heated about the meaning of these results, remember that benchmarks are good for one thing: measuring performance. Performance is important, but

Before getting heated about the meaning of these results, remember that benchmarks are good for one thing: measuring performance. Performance is important, but there is laundry list of other factors that programming languages optimize for. Because factors such as development pleasure, mean time to programmer error, and mean time to grok code are not easily quantified and compared, it's difficult to put two languages head-to-head on these often more important factors. These results clearly show how Rust and Go compare on a small set of performance problems. And if you're trying to solve any of these problems using either of these languages, and performance is what you're optimizing for — Rust is a clear winner. I wouldn't try to extrapolate these results to mean anything more than that.