Faster Python with Guido van Rossum
I have become increasingly convinced Python as a language is a &quot;trap&quot; for any use of notable scale, be the scale about number of developers, codebase size, or performance requirements.  It&#x27;s a great 0-&gt;1 language and great at simple glue, but eventually you hit a wall and have to keep investing larger and larger amounts of people or computing resources to get continued returns... all due to fundamental design decisions in the language from two decades ago that are quite difficult to fix.<p>Unless you go all-in on typing -- which is difficult today with any meaningfully sized existing codebase -- maintenance is largely a &quot;hope manual testing and unit tests catch anything resembling type errors&quot; which is a major challenge for, say, structural change to a code base like refactoring.  Plus typing is still young, the tooling somewhat immature, and can lead to false senses of security if you aren&#x27;t very careful and opt into the strictest modes.  This makes large number of developers and codebase size a major stumbling block.<p>The interpreter performance and GIL are fundamental issues as well.  Multiprocessing and hacks around the GIL are quite painful if you even glance at any native threading code (say in a C++ library) and even when you stick to pure Python, you have a debugging mess when anything goes wrong.<p>But if someone can improve performance, that&#x27;d be great, and has massive impact potential.  It is incremental though and doesn&#x27;t solve fundamental issues with the language.  I&#x27;m also skeptical of the &quot;5x&quot; plan referenced in the blog, and very skeptical we can ever see meaningful removal of the GIL due to library and baked in design decisions in existing code.  This means performance will fall further and further behind compiled languages.<p>(I write all of this having been a part of supporting Python at massive scale for over two decades, including at two FAANG companies who invest heavily in it.  I&#x27;ve seen the curve and the pain it&#x27;s caused, and would never use it for any code that needs to be performant or actively developed on the multi-month or year timescale).