In general the haskell community is helpful with novice programmers interested in learning concepts, but it is very hostile to novice programmers with a practical standpoint. It is not acceptable for many practical programmers that for a simple console program it would be necessary to chain three monad transformers when this is not really necessary. Unless the newcomer is willing to accept it. That reinforces the prejudice of the community against practicality in solving real problems. The result is a community that can discuss for hours how to calculate the factorial of a number or what kind of fold-map is more pretty or if lenses are comonadic metafunctors.
It is an error to introduce people to program in haskell using category theory. Is like if you teach your kid to handle his money starting with "John let me say you something: money is isomorphic to the rational numbers and rational numbers form an algebra. son consider a structure {N,+.*} where...."
It is the same that teaching music by first imposing three years learning musical notation. Or teaching a language by his grammar.
If so, all other languages should also be teached using CT, since the underlying structure of imperative programming is also CT.
Moreover it happens that the practical people are the ones that tend to think out of the box. Innovation requires some kind of disrespect for what is settled. Solving problems that nobody has solved already requires this kind of disrespect too. An excessive formalistic mind lives in a box from which it can not scape. It is like a bureaucracy of the mind. This creates the atmosphere for a kind of cargo cult religion that I mentioned above. If this is a religión, it is not mine.
I think that the Haskell community has to think seriously the reasons for his incredible success and influence as well as his almost complete failure in practical application in the Industry. And why, if some haskellers have success in the real world, they almost invariably disconnect from the haskell community.