Thanks... but the alioth benchmarks do not really measure production readiness, although they are very educational. To me it seems that for writing high perfor

Thanks... but the alioth benchmarks do not really measure production readiness, although they are very educational. To me it seems that for writing high performance dense numerical code the tradeoff still is: either write idiomatic code in a horrible language, or write horrible kludges in an beautiful language. Sigh. Would there be any "Scientific Haskell" resources available that would straightforwardly explain how to write performant code that wrangles data from one data sequence to another?