[jim-jim-jim]

Haskell is the "deep end" in terms of its ideology, but not difficulty. In practice, I've found compromise languages like Typescript and Scala more challenging because they're everything to everybody. If you already enjoy the benefits of types and want to explore that avenue further, then Haskell makes more sense than some of the alternatives.

[blueslurpee]

Insightful comment. In general I prefer tools that have a prescribed way of looking at the world and don’t try to be everything to everyone. That said, I feel a certain allure to the depth and “wizardry” that I’ve heard so much about in Scala, which doesn’t generally fit this mold.

So at the moment I really think I’m stuck between Scala, Haskell, or Elixir.

It’s tempting for people to simply say, “Learn all of them” but for practical reasons that’s not possible at the moment. So thanks a lot for your comment.

[jim-jim-jim]

For what it's worth, I write Scala professionally. I don't think I'd be nearly as successful with it if I hadn't learned Haskell first. ymmv, but it's helpful to divide and conquer. Haskell is a much cleaner way to "learn FP." You can take almost all of that knowledge and staple it onto Scala later. Learning the universal and ultimately quite simple concepts that comprise FP alongside the Scala language itself seems needlessly painful. The noisy syntax and compiler quirks will obscure whatever wisdom you're hoping to squeeze out of the process.

So yeah, learn Haskell, then make money with Scala.

[JoelMcCracken]

I would advise looking at Haskell. There is just so much there, and while you learn it you get so much exposure.

Elixir is def cool but keep in mind that it is just much more normal of a language. You can probably learn it in a few weeks. Haskell is a much longer journey

[blueslurpee]

Okay, I think this and the sibling have tipped it. Sounds like Haskell is where I will land and the best place to start branching out. Appreciate you!