Unfortunately there are folks that believe we have to use Python, and then rewrite in C, while calling those wrappers "Python" libraries, regardless of how much I would like to use JVM or CLR instead.
So if Python has taken Lisp's place in AI, I would rather that it also takes the JIT and AOT tooling as well.
Well, then, I guess, I should've prefaced what I wrote with "ideally".
Of course, there are circumstances we, the flesh-and-blood people cannot change, and if Python is all there is, no matter how good or bad it is, then it's probably better to make it do something we need... One could still hope though.
The pressure from slow and steady Julia's adoption, Mojo arriving into the scene, Facebook and Microsoft jumping into the JIT story, changing CPython team opinion on the matter, still leaves some hopes it might happen.
However now having Pytorch, Tensorflow and ONMX exposing the underylying native libraries to more programming languages, might mean to leave Python as it is, and use the other programming stacks for production.
I’m very excited about Mojo as a Rust 2.0 with first-class Python compatibility and support. Who knows if it’ll take off, but I love the project’s ideas and respect its ambition.
So if Python has taken Lisp's place in AI, I would rather that it also takes the JIT and AOT tooling as well.