I’d love to see some of the codebases where people complain about performance so I could profile them myself. Would put money on being able to improve the situation by orders of magnitude without switching stack.
We use Python on the backend of our web app for realtime image recognition and it’s fine because we’ve been thoughtful about data structures and algorithms.
I have no qualms with python. But Python is the high fructose corn syrup of programing languages... It's in everything.
It's dead easy to write out c bindings so from ML to Math to big data tasks it forms the glue to a lot of things.
My question is: is your real time image processing IN python or in C that python calls out to?
My point is that for most usecases you can go a lot further by looking at the code that’s running rather than the language that’s running it.
One big issue i have though: the lack of easy multithreading reduce your possibilities, or at least limit your creativity: you will often choose to use async/await (and sometimes use signals) rather than use producer-consumer designs, which are often the optimal solutions.