I’m not sure how this is related to its parent comment thread, but in any case I agree with it, and would view this as supporting my point. In my experience, a

I’m not sure how this is related to its parent comment thread, but in any case I agree with it, and would view this as supporting my point. In my experience, a big lukewarm codebase is exceedingly rare, and often gets that way because there was premature optimization in the form of assuming the project had to be written in this or that language way back at the beginning, without there ever having been a prototype stage when multiple implementation languages were actually tested. And even given that, it takes a special kind of alignment of the stars for the usage patterns, resource limits, and language tools to all work out properly for a system with few hotspots. But regardless, I do agree there are plenty of cases when it can be the right choice to presume a need to write the whole thing in C/C++. Examples become irrelevant though when they try to do a horse race comparison of a contrived, unoptimized Python example with a C/C++ example that would be more optimal out of the box just due to intended differences in the languages. Because these examples are exactly like targeted hotspot optimization, which would be the case when Python augmented with Cython/numba is a stronger contender.