Alternatively, we could do apples-to-apples comparison of the benchmarks. Go and C# are so similar that for benchmarks you can transliterate one into the other

Alternatively, we could do apples-to-apples comparison of the benchmarks. Go and C# are so similar that for benchmarks you can transliterate one into the other. We should be comparing programs that are comparable. My point is that BenchmarksGame is not comparing comparable programs. Code for some languages has extreme optimization, including doing things that most people don't do in day-to-day programming. Go supports assembly. Given enough time I could probably implement a given benchmark in assembly, beating C# (and pretty much anything). This is used to good effect in Go runtime and some really niche applications but in real life I don't have infinite amount of time to micro-optimize my code and write parts of it in assembly. What I want to know is the performance of competently written code.