See that is why I eventually decided against Haskell. There are just too few Haskell jobs so investing that amount of time from a career perspective makes little sense. That leaves hobby projects. And it just does not seem to make sense to me to spend that much time on a hobby, when you got plenty of other powerful languages you can learn in a fraction of the time and do more useful stuff with.
As an academic project language it seems great, but for practical work I just don't see it.
I can do a fair amount of functional programming in Swift and Julia, but still make useful stuff without without an huge mental investment.
My life as a professional C++ programmer has made me very negative to anything involving unreasonable complexity.
I agree with you. I don't regret the time I invested in Haskell but the payoff isn't obvious. C++ is a very different kind of complexity though, it is so easy to get burned by something that compiles but fails at run-time or is very inefficient due to an issue you didn't know you didn't understand. The Haskell compiler may make you want to throw your computer through a window but you won't think everything is fine when its not.
I've found it quite practical for getting things done, there's a higher learning curve then something like python though. From a career perspective it's hard to recommend anything that isn't one of the top most used programming languages, I'm not sure Haskell or most functional programming languages can do anything about that though.
As an academic project language it seems great, but for practical work I just don't see it.
I can do a fair amount of functional programming in Swift and Julia, but still make useful stuff without without an huge mental investment.
My life as a professional C++ programmer has made me very negative to anything involving unreasonable complexity.