Nothing wrong with writing a book, but frankly,what Haskell really could use is a richer ecosystem, better tooling (ahem cabal) and perhaps a sense of its niche

Nothing wrong with writing a book, but frankly,what Haskell really could use is a richer ecosystem, better tooling (ahem cabal) and perhaps a sense of its niche(s). I like Haskell, but there's absolutely no reason why you ought to expect people to start using it when you've got much richer, usable ecosystems available out of the box. History keeps repeating itself. What makes or breaks a language isn't just the language itself. A language needs a supporting ecosystem to actually make it useful. Of course, it's a bit of a Catch-22: you need people to populate the ecosystem with code. So why don't we start with a leiningen for Haskell? Time and again, the forums reinforce that the basic tools are what keep them from treating Haskell seriously.