&gt; The problem, economically speaking, is that Haskell and Clojure engineers are massively underpaid, when you consider that an average Haskeller would be Principal+ at any Java shop. That&#x27;s because the Java and C++ people can create bidding wars every year and spike their salaries, whereas using a better but more niche language makes that career strategy untenable.<p>I haven&#x27;t found the same to be true for other languages, but in my experience the Average Haskeller is so caught up in academic exercises, technical one-upmanship, and code golf shenanigans that I&#x27;m surprised they find any time to contribute any business value at all. Having a discussion about acceptable levels of technical debt with a Haskeller is like having a discussion about acceptable levels of meat products in your diet with a vegan in a world where there are no plant foods...<i>&quot;everything is technical debt, and none of it is acceptable, and we absolutely can&#x27;t move on until we change all relevant functors to applicatives and all nested record accesses to lenses!&quot;</i><p>And it is squarely a cultural issue, not a technical one...it is quite obvious that Haskell is a fantastically powerful language and capable of mowing over most enterprise-y languages with ease for a very wide variety of domains. Its just that Haskellers are so nitpicky about elegance and style that they don&#x27;t know how to let shit be shit and get something done when it is needed.<p>This obviously isn&#x27;t the only case for Haskellers. Looking at JGM&#x27;s github feels like looking at Dumbledore&#x27;s magic through the eyes of a Muggle. It just feels that way with the average Haskeller that I work with.