From: Isaac Gouy Date: 2005-06-11T06:20:29+09:00 Subject: Re: python/ruby benchmark. Austin Ziegler wrote: > On 6/10/05, Isaac Gouy wrote: > > There isn't with benchmarks per-se; there can be a problem with > > how one chooses to interpret benchmarks. > > No, it's the benchmarks themselves that are the problem. Remember > that NVidia got caught detecting a benchmark in their drivers and > optimizing output for the benchmark. > > Similarly, this thread was started because someone came across your > language shootout benchmark page and assumed that Ruby is > dramatically slower in Real Life Examples because it's slower in the > benchmarks. As I said - There isn't a problem with benchmarks per-se; there can be a problem with how one chooses to interpret benchmarks. > Which, I can assure you, it most assuredly NOT. Not "dramatically slower" than what other language, for what specific "Real Life Examples"? > It's hype, but the idea that Rails makes one 10x more productive is > part of the value of Ruby. Unless your program is of a special case > -- and a lot of these special cases are handled already -- then Ruby > programs will be developed faster and more easily maintained than > their non-Ruby counterparts. Enough so that execution speed is > something of a wash. Faster to develop-in than what other languages - Smalltalk? Lisp? Mathematica? > At any rate, I consider the Alioth shootout to be harmful to all > languages involved. There is no useful value provided by it, > especially as it does not permit language-appropriate modifications > to the algorithms in use. What's a language-appropriate modification? Have you ever asked for one to be accepted in the Alioth shootout?