2 ms·
The thing is, like 20% of your program ends up being non-idiomatic, ghc-specific Haskell. I suppose for certain applications it could end up being the whole thi
by whateveracct 7y ago
The thing is, like 20% of your program ends up being non-idiomatic, ghc-specific Haskell. I suppose for certain applications it could end up being the whole thing, but in general I'm thinking optimized Haskell is in that ballpark tops.
And idiomatic Haskell's performance is plenty acceptable for a variety of common use-cases (so not "nearly always is")
- coolplants 7y agoIn my experience that has not been the case. Either unacceptably slow computation or High memory usage.
- whateveracct 7y agoI mean, what use-case was this? I've deployed plenty of web services & data processing jobs in Haskell and the RTS has never been a bottleneck or issue. So I'm guessing you weren't doing an IO-bound activity (where Haskell is quite good.)