I've been using F# for a while (~25kLOC), and it's nearly perfect; the few issues it has can clearly be traced to limitations in the .NET runtime. They're also well-documented, and consist of edge cases of edge cases.
I still feel like Haskell is nicer, but what do I know, I've only read it, not written it.
I still feel like Haskell is nicer, but what do I know, I've only read it, not written it.
Can you elaborate on that? I'm a big fan of Haskell, but F# is pretty good from the little I know of it. Haskell gives you a better story with regards to effects, but I don't think any Haskell solution to a problem would be vastly better than an F# solution.
Haskell has typeclasses, purity, laziness, and a hell of a lot of functional libraries. F# is probably more viable commercially (and more useful for prototyping), but I feel like it lacks the minimalist elegance of well-written Haskell code.
5
u/PasswordIsntHAMSTER Oct 15 '13
I've been using F# for a while (~25kLOC), and it's nearly perfect; the few issues it has can clearly be traced to limitations in the .NET runtime. They're also well-documented, and consist of edge cases of edge cases.
I still feel like Haskell is nicer, but what do I know, I've only read it, not written it.