That is one thing I don't like about the shoot out, even when you don't want it to be about performance it still is. When they measure code size they only measure the best performing app. They don't have a separate set of measurements for concise code. So most of the FP entries are C in an FP skin.

> When they measure code size they only measure the best performing app.

1) Not true, the code size of every program contributed is measured.

The smallest meteor-contest program shown is a Haskell program which takes almost 4 times longer than the fastest Haskell meteor-contest program.

http://shootout.alioth.debian.org/u64/performance.php?test=m...

2) True, the benchmarks game code-used comparison is between the fastest programs for each of the programming language implementations.

The size of programs written to be fast - compared to - the size of programs written to be fast.

3) True, there isn't a separate set of measurements for concise code, or least memory-used code, or most obfuscated code, or ...

You can fork a project to collect concise code data!

>> So most of the FP entries are C in an FP skin.<<

Do you think that's the only way to write fast FP code?

Thanks for that, I didn't realize they had updated the site so much.

Do you think that's the only way to write fast FP code?

That is typically how you go fast in OCaml.

Haskell people are working on making idiomatic code fast. But even there, writing C in Haskell is often the way to go for pure performance.