3 ms·

Everything is worth learning f but if you can only learn 1 thing today should that be Haskell or something else?

• blowski 3y ago
  What would you be trying to get from learning something? If you’re wanting to improve your understanding of FP, could be great. If you want to “become more employable” it’s probably waste of time, because it only helps in a very narrow niche. Or maybe you just want to have fun!
• xupybd 3y ago
  I started with F# and found that very worthwhile. I'm not sure about Haskell. I suspect it's a new level of complexity.
  • consilient 3y ago
    Haskell is much simpler than F# in its full .NET multi-paradigm "glory" but moderately more complex than the fragment of F# used in idiomatic functional code.
    • xupybd 3y ago
      Thanks, that's good to know. One of the things drawing me to learn Haskell is Higher-Kinded Types. I'd really like to learn about them and have a play. Higher-Kinded Types seem complex to me but until I have a play I wont know. The other thing that makes me think Haskell is harder is that functional code is enforced, while in F# it's simply the default. I'm not sure what impact this will have on complexity of real world applications. But in F# it's really easy to have an imperative shell and functional core.
      • nequo 3y ago
        Pick a toy project and do it in Haskell. There’s no better way to find out what FP being enforced means for you.