4 ms·

I want to ask an annoying question. Why F# and not haskell?

• adgasf 8y ago
  The main reason was that team had more experience with F#. I think it is also more approachable than Haskell for OOP devs (C# to F# comparisons are quite common on the internet). I'm sure Haskell would also have been an excellent choice though :)
• BeetleB 8y ago
  Not OP, but some reasons usually thrown around: F# has the power of .NET and its libraries behind it. Haskell's insistence on purity and laziness does increase the time it takes to design things well. F# makes it easier to violate purity in controlled ways, and is not lazy be default. People who've used both say it's a lot easier to get lost in abstractions with Haskell, and there doesn't appear to be a clear "stopping" point. A common statement by people who move from Haskell to OCaml/F# is "I spent N years on Haskell but didn't produce much. In 6 months of (OCaml|F#) I've produced more than in those N years with Haskell." The bottom line: The .NET libraries and slight relaxing of purity/laziness allows for more productivity. (I'm not an expert on either - just repeating what you normally find in the threads).
• nikofeyn 8y ago
  f# is a multi-paradigm language. it allows you choose what paradigm fits the problem best and allows you to easily mix paradigms, and it does so in a clean way. haskell does not have this flexibility. this is f#'s power.