5 ms·
From the paper... Second, to make the comparison as unbiased as possible, we coded the same algorithm in each language without adapting it to the peculiarities
by k2enemy 12y ago
From the paper...
Second, to make the comparison as unbiased as possible, we coded the same algorithm in each language without adapting it to the peculiarities of each language (which could reflect more about our knowledge of each language than of its objective virtues).
They have invited others to fork the code on github and write the fastest possible for each language.
- bradfordarner 12y agoThank you for the note. I hadn't visited the github yet. I will be interested to see whether people can whittle down the respective benchmarks.
- Alupis 12y ago^^ This is not "unbiased"... in their attempt to make it unbiased, they introduced a huge amount of bias. They wrote the code for each language based on prior knowledge about each language, and/or from likely googling how-to's... far from performant code with any language. A mild understanding of each language could yield dramatic performance improvements over not understanding it at all.
- igouy 12y agoThis is not "as unbiased as possible" -- it is biased towards the initial form of algorithm description. To make the comparison "as unbiased as possible" would be to code the same algorithm but adapt it to the peculiarities of each language implementation.