Python needs to be compiled into machine language to ever have a chance of competing on speed. We can already get around the GIL with multiprocess but Python is still to slow even when not bound by copying memory between processes.
As for multiprocess, I currently have 150 python process running on the work cluster. Each doing their bit of a large task. The heavy lifting is in a python library but it’s C code. but it’s actually not bad performance wise and frankly wasn’t to bad to code up. I think for my use case threads would make it harder.
Maybe Im liking python more over time..
JavaScript interpreters that people actually use, have a JIT inbox.
Both Java and Javascript are ultimately compiled into machine code, through JIT. And this matters because Python doesn't have JIT.
Even Ruby, that is historically a way slower language, is gaining JIT nowadays. Python has got no excuses.
And it is also about flexibility. What I love about Python is the simplicity, and let's be honest, multiprocess anything but. Especially if you fall into one of the gotchas (unpickable data for example).