qstwall
Re:A viable solution for Python concurrency
on Saturday October 16, 2021 @03:47AM (#28886250)
It will still be slow if the threaded code is in pure Python.
Re:A viable solution for Python concurrency
on Saturday October 16, 2021 @03:43AM (#28886235)
It took several years to migrate Twisted or NumPy. The 10 years is the cumulative pain of having 30% of packages not migrated yet. It took at least 7 years to have 90% migrated.
Re:A viable solution for Python concurrency
on Saturday October 16, 2021 @03:40AM (#28886228)
It is hard to see the point of a GIL removal that will destabilize the C extension ecosystem for probably a decade again:
C extensions can already start as many threads as they like. Threaded pure Python, even if GIL-less, is still slow, so what is the point?
The whole point of Python (before asyncio, pattern matching etc.) was being simple and having a nice C interface. If that continues to erode, people will (and should) look at other languages. C++ for example is pretty Pythonic these days, Java does not have these problems, Erlang (while slow) was written for concurrency from scratch, etc.