[kmiroslav]

> 2. Once you learn Haskell you really kind of want a Haskell job to put all this nice stuff into practice.

Personally, not really.

I enjoy dabbling with Haskell on my open source projects but doing so has made it abundantly clear why I would never want to use it on a production system, especially one I'm responsible for. Laziness making performance intractable, bad tooling (see the stack trace observation above), difficulties hiring Haskell programmers and the fact that while they can be good coders, they are usually very weak on the engineering side, etc...

Both Haskell and Scala are on my list of languages that I love to experiment with on my free time but that I think are not ready for mission critical stuff.

> you have a pool of people who have self selected to be above average in determination and smarts

I hear this claim a lot from Haskell programmers but this has zero evidence.

It's just a human thing to believe that your choices of technology make you better than people who made different choices.

[the_af]

> Both Haskell and Scala are on my list of languages that I love to experiment with on my free time but that I think are not ready for mission critical stuff

I find this curious, since both languages have been successfully used for mission critical stuff, and in particular Scala is deployed for mission-critical enterprise applications. At my day job, for example, but this is starting to look even more common, judging by the recruitment emails I get.

[_0w8t]

I am curious what makes Scala in your opinion enterprise unready? It is the same JVM in the end and learning curve for a Java programmer is not that high.

[Retra]

I've learned a good number of languages, and Scala has been one of the most contrived, in my experience. Even for a Java developer.