> From: Russel Winder <[email protected]> > Sent: Monday, December 19, 2011 11:29 PM
As for your other comments: > The opening page does indeed set out that you have to be very careful with > the data to avoid comparing apples and oranges. No, the opening page says - "A comparison between programs written in such different languages *is* a comparison between apples and oranges..." > Actually I am surprised that Java does so well in this comparison due > to its start-up time issues. Perhaps the start-up time issues are less than you suppose. The Help page shows 4 different measurement approaches for the Java program, and for these tiny tiny programs, with these workloads, the "excluding start-up" "Warmed" times really aren't much different from the usual times that include all the start-up costs - http://shootout.alioth.debian.org/help.php#java > Part of the "problem" I alluded to was people using the numbers > without thinking. Do you include yourself among that group of people? > I started a project with the Groovy community to provide reasonable version > of Groovy codes and was getting some take up. You took on the task in the first week of March 2009 http://groovy.329449.n5.nabble.com/the-benchmarks-game-Groovy-programs-td366268.html#a366290 and iirc 6 months later not a single program had been contributed ! http://groovy.329449.n5.nabble.com/Alioth-Shootout-td368794.html > In the event, Isaac took Groovy out of the Shootout, so the Groovy > rewrite effort was disbanded. Your "Groovy rewrite effort" didn't contribute a single program in 6 months ! > There is no point in a language development team running a benchmark. Tell that to the PyPy developers http://speed.pypy.org/ Tell that to Mike Pall http://luajit.org/performance_x86.html Tell that to the Go developers
