Four months with Haskell
I programmed Haskell professionally for about a year and a half. My last company has been trying to hire Haskell engineers for over 2 years and we&#x27;ve only managed to hire at least 2. &quot;Hiring Haskell developers is not hard&quot;, is extremely subjective and naive to say the least. Obviously, YMMV, but the front-end devs that the last company was hiring was running laps around the Haskell team. Honestly, finding a Haskell engineer is not always a winner either. I&#x27;ve found that the ones we hired are very smart but not very decent engineers (i.e. defining requirements, shipping a product on time, understand tradeoffs, etc.).<p>There were quite a few things about Haskell that I truly love and miss, such as the type system, but the tradeoffs just weren&#x27;t worth it to me and I honestly don&#x27;t think it&#x27;s mature enough to be considered &quot;enterprise ready&quot;. Aside from the learning curve, there were several bugs in one of the Haskell libraries that caused frequent outages (until we were able to pinpoint what was wrong), lazy evaluation caused excessive memory bloat when used incorrectly, and my all-time favorite: needing to switch on profiling in order to get stack traces (this is suppose to change in future GHC versions) which defeated the whole purpose of &quot;haskell is fast&quot;. I don&#x27;t know, perhaps we were using Haskell wrong. From a business perspective, it just wasn&#x27;t making that much sense given how difficult it was to hire, getting engineers excited to learn it, and having the features needed to monitor a production system.