[kibwen]

For comparing multiple implementations of a single benchmark in a single language, this sort of data would be interesting as a 2D plot, to see how many lines it takes to improve performance by how much. But for cross-language benchmarking this seems somewhat confounding, as the richness of standard libraries varies between languages (and counting the lines of external dependencies sounds extremely annoying, not only because you have to decide whether to include standard libraries (including libc), you also need to find a way not to penalize those for having many lines devoted to tests).

[benstrumental]

Not exactly what you're looking for, but here are some 2D plots of code size vs. execution time with geometric means of fastest entries and smallest code size entries of each language:

https://twitter.com/ChapelLanguage/status/152442889069266944...

[simion314]

And when you want to make the code readable you try to space things out, split things in small functions, use longer and clear variables name. I guess they are asking for running the code trough a minifier so their implementation gains some points.

[benstrumental]

I can't find the documentation for it, but you can see here that they measure the size of the source file after gzip compression, which reduces advantage of code-golf solutions:

https://salsa.debian.org/benchmarksgame-team/benchmarksgame/...

[igouy]

"How source code size is measured"

https://benchmarksgame-team.pages.debian.net/benchmarksgame/...

[benstrumental]

Thanks Isaac. How do I reach that page? I expected it on one of the informational pages such as the home page or benchmark programs page, but had no luck.

[igouy]

There's a "How programs are measured" link on these pages which show measurements:

https://benchmarksgame-team.pages.debian.net/benchmarksgame/...

:and these pages:

https://benchmarksgame-team.pages.debian.net/benchmarksgame/...

:and these pages:

https://benchmarksgame-team.pages.debian.net/benchmarksgame/...

[kibwen]

On other benchmarks they measure the size of source code after it's been run through compression, as a way to normalize that. Not sure if that's been done here, but it should be.

[igouy]

Yes, they're the same measurements.

[mrtranscendence]

I'm not sure I see the problem. What does it matter that program A is shorter than program B because language A has a richer standard library? Program A still required less code.

[kibwen]

Because that's not what's being measured here, you're also mixing in performance, and it's impossible to tell at a glance whether a score is attributable to one or the other or both.