[crote]

> In any case, those are not real concerns when programming with Haskell.

They were my concerns when learning Haskell - and I was following graduate-level courses at a university which contributes rather heavily to the Haskell ecosystem. They might not apply to you, but that doesn't mean they aren't real.

My limit was seeing a HTTP server being praised over and over again for it's wonderful type-safe API, trying to use it, and a few weeks in discovering that a very basic HTTP feature was considered an "open research question" and "would probably require a full redesign". Having poor compile time and consuming a crazy amount of memory was indeed also quite an annoyance. Having an entire ecosystem seemingly more concerned about writing theses about type theory than with building usable libraries? That was a dealbreaker.

Haskell is a great tool for programming language research, and I can't wait to see what kind of crazy things they'll end up doing with dependent typing. Unfortunately in my experience this also seems to make it into a rather poor choice for actual programming in a non-research environment.

I don't hate or dislike Haskell. If anything, I'm disappointed in it. I really want to love it and use it for everything, but it's just... not there yet.