But many dev shops just want a pool of cheap labour and care little about robustness. And the abundance of cheap labor is a function of both learning curve and critical mass.
I gather this is not a design goal of a language with "avoid success at all costs" as an unofficial motto
The extra difficult-to-learn parts of Haskell makes for programs that are more practical, shorter and easier to work with.
There's a trade-off between simplicity and power - and we don't really want to maximize simplicity only. And if we did, Java would not be a good candidate either.