Haskell Problems for a New Decade
&gt; “ Many of the large tech companies are investing in alternative languages such as Swift and Julia in order to build the next iterations of these libraries because of the hard limitations of CPython.”<p>I would be interested in evidence of this. I work at a big tech company in ML and scientific computing, and have close peers and friends in similar leadership roles of this tech in other big companies, FAANG, finance, biotech, large cloud providers, etc.<p>I am only hearing about the adoption of CPython skyrocketing and continued investment in tools like numba, llvm-lite and Cython. At none of these companies have I heard any interest in Julia, Swift or Rust development for these use cases, and have heard many, many arguments for why Python wins the trade-offs discussion against those options.<p>In fact, two places I used to work for (one a heavy Haskell shop and one a heavy Scala shop) are moving away from those languages and <i>to</i> Python, for all kinds of reasons related to fundamental limitations of static typing and enforced (rather than provisioned) safety.<p>I mean, Haskell &amp; Scala are great languages and so are Julia &amp; Swift. But even though in some esoteric corners people have started to disprefer Python, it’s super unrealistic to suggest there’s large movement away from it. Rather there’s a large move <i>to</i> it.<p>It reminds me of the Alex Martelli quote from Python Interviews,<p>&gt; “Eventually we bought that little start-up and we found out how 20 developers ran circles around our hundreds of great developers. The solution was very simple! Those 20 guys were using Python. We were using C++. So that was YouTube and still is.”