Leaving Haskell behind
As someone that has also written haskell for about a decade and moved away from it as a breadwinner recently (but for other reasons - I simply wanted to filter job offerings based on social utility rather than language stacks), I definitely agree with the author&#x27;s first point: the Haskell community values learning extremely strongly. That&#x27;s great because you work with curious people that have always something to teach and learn. But the community is not so strong when it comes to discard ideas after trying them, and so a professional haskell codebase, if not curated strictly, often ends up with lots of things that you <i>can</i> do but that you probably <i>shouldn&#x27;t</i> use.<p>I, however, disagree about tooling. Haskell&#x27;s tooling sucks, but having used several other languages since (python, js, java, rust, elm), most tooling sucks. After this tour, I miss the Haskell toolchain. Sure, cargo is great, but that&#x27;s one in many, and most older languages don&#x27;t have this. I wonder whether Rust can escape this fate as it ages. The author also mentions being dismayed by Python, so I guess that&#x27;s mostly me seeing the glass half-full though.