Re:Why Lisp is a Big Hack and Haskell is Doomed to Succeed (...
by platz on Sunday March 30, 2014 @06:40PM
(#7498297)
If by LINQ you mean the map/filter/fold crew, I think this may be selling Haskell a little short. You could say the same about python. At least F#'s computation expressions give you the full power to create your own monads with it's "computation expressions", and in LINQ things are more statically locked down.
Re:Why Lisp is a Big Hack and Haskell is Doomed to Succeed (...
by thirsteh on Sunday March 30, 2014 @06:52PM
(#7498335)
Right -- I wasn't sure whether F# would be considered "practical" in this case.
Re:Why Lisp is a Big Hack and Haskell is Doomed to Succeed (...
by platz on Sunday March 30, 2014 @07:04PM
(#7498367)
I guess F# isn't practical if you're building a WPF application (I agree the tooling is lacking). Otherwise it seems like it can do everything C# does (including mutation, classes, interfaces, properties), only with a slightly unfamiliar (at first) syntax.
LINQ is "practical Haskell," so is most of Rust (if "practical" means approachable to imperative programmers.)
Besides being on the JVM (which is a big plus), Scala hardly makes anything more practical than it is in Haskell. In fact, Scala programmers tend to migrate to Haskell (and ML languages) rather than the other way around.