As a paid user of haskell and Java, here are a few of the things I experienced when discussing about language choices in corporate settings: * Fail a project i

As a paid user of haskell and Java, here are a few of the things I experienced when discussing about language choices in corporate settings: * Fail a project in Java, and you have a project failure. Fail a project in Haskell, and you have a Haskell failure. * Management has a large veto power, and management usually favors technologies they are used to, or used to use themselves. * Management also favors their ease of work with the tech. In practice, they often hold the belief that it's much easier to find java developers than it is to find haskell developers. * Haskell suffers from a reputation of being "academic" and "hard to do real things with". In practice, I've done great commercial projects in Haskell, and the technology was worth using. When done right, recruiting for haskell projects was much faster than recruiting for any mainstream language. On the flipside, it was sometimes hard to get adequate corporate stewardship for the language (for instance, managers/HR insisting they found no one for the job after publishing through the usual channels when you know half a dozen people at the local meetup that would jump ship if offered a position).