Comment on Part 2 Dart vs Go vs Python (and PyPy) PerformanceparentComments−hartror14yAh thanks! So nothing to do with GC or poor IO but a poorly selected operation to do in a benchmark.−drivebyacct214yAs it seems like is always the case in these fairly naive benchmarks. (Not specifically about Go here, it seems like people often cite python when they're really using some optimized C code).−berntb14y>>poorly selected operation to do in a benchmark.Considering the history of benchmarks, it is quite likely the opposite: The library was selected very carefully, to argue a "point". :-(
Comments
Ah thanks! So nothing to do with GC or poor IO but a poorly selected operation to do in a benchmark.
As it seems like is always the case in these fairly naive benchmarks. (Not specifically about Go here, it seems like people often cite python when they're really using some optimized C code).
>>poorly selected operation to do in a benchmark.
Considering the history of benchmarks, it is quite likely the opposite: The library was selected very carefully, to argue a "point". :-(