Other than that, there is really not much that I don't like. I think it's one of the best languages I've tried and I wish it was more widely used in the industry.
That's life folks. Some people just need to build products and get them to market for paying salaries and supporting their family. If you ask me what is bad about Haskell, it is the difficulty in finding developers and difficulty on making other developers to work with apps written in Haskell.
I don't program in Haskell, I have people doing the programming side (don't get me wrong, I wrote 100k LOC in Java over the 12 months) and if I ask other developers around here to learn Haskell, it is difficult to get any enthusiasm.
"if I ask other developers around here to learn Haskell, it is difficult to get any enthusiasm." What you are saying is that you have developers who are not willing to learn new technologies. It is one thing to say that they've spent some time studying it and decided that it wasn't a good fit for the problem they are working on, it is a completely different thing to say that they don't know it and are not interested in learning something new and don't want to hear about it. I would question the quality of such developers.
This makes me wonder even more what's wrong with it! I doubt the learning curve is scaring THAT many people away, since employable programmers already demonstrated a willingness to learn hard things. It seems to me that there must be something bad I don't know about the language.
No, there isn't. People are just scared because of what they hear from others who failed at learning it, and who now say negative things about the language to feel better about themselves. People who fail to learn it are too entrenched in another paradigm or aren't able to think abstractly enough. It's not the language's fault. It might be partly because they read the wrong learning materials.
> and if I ask other developers around here to learn Haskell, it is difficult to get any enthusiasm
Sorry, it does not seem to be Haskell the problem, but the people.
> If you ask me what is bad about Haskell, it is the difficulty in finding developers and difficulty on making other developers to work with apps written in Haskell.
For this, I suggest few solutions: (1) http://www.haskellers.com/users (2) http://careers.stackoverflow.com/employer (3) http://www.reddit.com/r/haskell (4) https://wiki.haskell.org/Mailing_lists (5) #haskell at Freenode
In the extreme case, I would go for https://wiki.haskell.org/Haskell_in_industry and https://github.com/commercialhaskell/commercialhaskell looking for a freelancer or a consulting company focused on Haskell.
Seriously, I don't think those were strong arguments, although I totally understand the difference in finding a Java developer versus a Haskell one.
Surely you are not aware of what `cabal sandbox` (https://www.haskell.org/cabal/users-guide/installing-package...) is. Well, if it is your unique complain about Haskell, I think you should give it a second chance! :)
Then there is the "Chicken & Egg problem" behind libraries and adoption rate.
1. High Learning Curve = Lower adoption rate
2. Low adoption rate = Less people making libraries
3. Less Libraries = Less People want to use Haskell - Goto 2I think there are plenty of libraries.
I also think what people call "high learning curve" is more "this is so different from the good ol' OOP that I've been doing for the past decade".
Functional programming is not hard, it is actually very easy to learn as a first paradigm. It becomes more complicated when one has experience with a different paradigm and has to un-learn their habits to learn new ones.
For the partial problem, you could rely on `safe` (https://hackage.haskell.org/package/safe). But I am sure you could take any other function on `Prelude` that you don't like and do a Hayoo/Hoogle (e.g. http://hayoo.fh-wedel.de/?query=[a]+-%3E+Maybe+a )search and find the one more appropriate. :)