Hacker Newsnew | comments | show | ask | jobs | submit login

I don't know if you're trolling or cocksure, but no, that is not what I was talking about. I said the constraints create a bias, not the measurements themselves. For example, the performance measurements are biased against most garbage collected languages because the rules don't allow any options to fine-tune the GC's behavior (which can make a big difference). Obviously, there are no equivalent rules forbidding people from fine-tuning C++'s manual memory management.



If the rules don't allow any options to fine-tune the GC's behavior how do you explain the use of options to fine-tune the GC's behavior here:

http://shootout.alioth.debian.org/u32q/program.php?test=fast...

and here

http://shootout.alioth.debian.org/u32q/program.php?test=knuc...

and here

http://shootout.alioth.debian.org/u32q/program.php?test=mand...

and here

http://shootout.alioth.debian.org/u32q/benchmark.php?test=pi...

and here

http://shootout.alioth.debian.org/u32q/program.php?test=rege...

and here

http://shootout.alioth.debian.org/u32q/program.php?test=revc...

and ...

-----


Simply looking at the benchmarks game website shows that your general claim "the rules don't allow any options to fine-tune the GC's behavior" is wrong.

Do you have any other claims that can be checked?

-----




Guidelines | FAQ | Support | API | Security | Lists | Bookmarklet | DMCA | Apply to YC | Contact

Search: