Haskell is not particularly esoteric, but heavily opinionated. Libraries cannot change that basic fact - there are just problems it will be extremely unsuited

Haskell is not particularly esoteric, but heavily opinionated. Libraries cannot change that basic fact - there are just problems it will be extremely unsuited for. Java has some of the same problem by the way in reverse. (Package handling, forced garbage collection and unknown real time and memory usage characteristics.) The difference being that Java's core has much less important opinions about algorithms, while Haskell tries to make everything functional or it is awkward. So, while Haskell will be hard to use for problems best described in an imperative way (in addition to other issues say Java has), Java will only have serious problems where memory and runtime determinism are paramount. It so happens that a lot of the programming is done in imperative way. Including the libraries.