Re:Rust-Doom: A Doom renderer in Rust, with no unsafe code
by kibwen on Friday October 30, 2015 @02:48PM
(#10479732)
Your defensiveness is unwarranted and your interpretation assumes bad faith.
Programming languages whose dominant implementations are interpreted generally (though don't necessarily need to) provide less direct control over hardware, memory layout, and algorithms, and in practice will defer to C via FFI when such control is necessary. Because the benchmarks game generally prohibits calling out to C, it means that many "tricks" employed by low-level languages are unavailable to the higher-level languages. Whether or not this is a desirable property is up to the reader's interpretation.
Indeed, because it's essentially impossible to enforce anything like "idiomatic" code in any of the benchmarks game languages, and so whether a program is "cheating" is up to the reader's interpretation. That said, the fact that it is up to the reader's interpretation means that it is valid for some readers to conclude that some programs are "cheating", while other programmers may differ. Personally, I think the point is moot, and that microbenchmarks aren't worth getting so worked up over. :P
[ Parent
| on HN ]
Re:Rust-Doom: A Doom renderer in Rust, with no unsafe code
by igouy on Friday October 30, 2015 @03:02PM
(#10479816)
>>... is valid for some readers to conclude that some programs are "cheating", while other programmers may differ.<<
Which takes us back to the unanswered question --
Veedrac, are you saying that the benchmarks game programs you wrote "cheat" ?
Re:Rust-Doom: A Doom renderer in Rust, with no unsafe code
by kibwen on Friday October 30, 2015 @03:57PM
(#10480159)
I think you've overlooked this part of his comment:
"I say this as someone who spent a fair while optimizing the Rust benchmarks to use all of the hacks the other languages use"
Do you think the C, C++, Haskell, etc. implementations "cheat"? :P