This is really going to change the game for certain applications!
Being able to thread Python properly is really going to help it compete with NodeJS and JVM workloads (especially if they continue to work on proper JIT for Python).
For multithreaded applications, just don’t use python.
For multithreaded CPU-bound applications, just don’t use pure python, unless the intensive work is done in a compiled module. (Those have always been able to run without the GIL, there are a bunch of them in the standard library and other popular packages, and the API for writing custom ones is pretty good.)
FTFY
Python performance sucks - use C if it matters.
FTFY
C is one option for writing compiled modules, but certainly not the only one.
More importantly, writing a moderate-sized program entirely in C when only a small fraction of it needs high-performance custom behavior is likely a poor use of time, both immediately and throughout the code's life.
It is a bad language choice for that need but a lot of people don't have a choice or aren't the decision makers.
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Follow the wormhole through a path of communities !webdev@programming.dev
