Good to see them getting Nim-related [issues](https://github.com/tbrand/which_is_the_fastest/issues) / [pull requests](https://github.com/tbrand/which_is_the_fastest/pulls) (from anyone not boycotting GitHub, ahem...). Also remember [TechEmpower](https://github.com/TechEmpower/FrameworkBenchmarks/tree/master/frameworks/Nim).
> This is an important lesson why benchmarks shouldn't be trusted. Nothing should be "trusted", and no benchmark is perfect, but it's still a noble and useful sport. Optimizing for specific test cases shows a dev team's dedication to performance. It helped overcome the "Java is slow" stigma (which was true, at least on the desktop), and Go's fasthttp / Python's japronto are significant arguments for the viability of those respective languages.
