3 ms·
I actually think it has a lot to do with the runtime and perhaps a little with compilation time. Compared to the JVM languages I would choose Haskell any time
by ObscureScience 4y ago
I actually think it has a lot to do with the runtime and perhaps a little with compilation time.
Compared to the JVM languages I would choose Haskell any time (if given the choice), but for most native tasks the "burden" of Haskell's type system and mediocre performance makes it hard to pass the "value return" threshold compared to Go, Nim, Rust or even C++.
I'm sure that Haskell's performance is plenty for most applications, and the low level/unpure escape hatches are there, but they also raise the complexity significantly from that I have seen.
To me Haskell still has an aura of language research.
This may be a prejudice assumption, I have not done anything more than toys with it.
- kaba0 4y agoI don’t know, Haskell and Go absolutely plays in the same field regarding performance from a surface level analysis (and also in benchmarks) - both are compiled to native code with in-built GC, whose usage they can heavily cut back on compared to a traditional OOP language due to strong FP and value types, respectively. Whether it means you should lower your expectations for Go or raise them for Haskell, is up to you but Haskell can be a quite performant language for many kinds of problems - even if laziness may make performance reasoning harder.