Why most programming language performance comparisons are most likely wrong
The author raises interesting points, but none of them are novel.  The general tone here seems to be along the lines of: there are just so many moving variables, no fair comparisons may be fairly made.  But I judge such positions agains this heuristic: &quot;But, is it actionable?&quot;  Pragmatism demands we at least take a glance at languages, frameworks, and platforms from the perfromance perspective.<p>Here is a practical example: There may be some issues with the Tech Empower web framework benchmarks, but -- across a battery of tests -- one may clearly discern that there are NO python or ruby frameworks in the top 75% performing web frameworks yet plenty of go, Java, and PHP frameworks there.  c++, js, amd rust dominate the top 20% and the differences in requests-per-second among them, statistically less significant, literally engulf the total rps numbers for the python or ruby rps totals.  If you (or your company) are paying cloud fees for hosting your services (including serverless), you are absolutely throwing money away, perhaps for a &quot;good&quot; reason (&#x27;we have a huge rails codebase&#x27;), if you ignore this information.