This post originated from an RSS feed registered with Agile Buzz
by James Robertson.
Original Post: Censoring Benchmarks - redux
Feed Title: Cincom Smalltalk Blog - Smalltalk with Rants
Feed URL: http://www.cincomsmalltalk.com/rssBlog/rssBlogView.xml
Feed Description: James Robertson comments on Cincom Smalltalk, the Smalltalk development community, and IT trends and issues in general.
Dare Obasanjo explains - unofficially - some of the rationales for censoring benchmarks:
I'm not sure what the official line is on these contracts but I've come to realize why the practice is popular among software vendors. A lot of the time people who perform benchmarks are familiar with one or two of the products they are testing and know how to tune those for optimal performance but not the others which leads to skewed results. I know that at least on the XML team at Microsoft we don't block people from publishing benchmarks if they come to us, we just ensure that their tests are apples-to-apples comparisons and not unfairly skewed�to favor the other product(s) being tested.
Yeah, I understand that theory. I'd rather be open, and meet bad speech with more speech though. Regardless of your reasons, having a license that forbids benchmarks without prior approval is going to come across as hiding something