@isaaclyman
That's pretty much how #Python optimizing compilers like #cython, #mypyc, #numba, and #TaichiLang work, and iiuc is the idea behind #MOJOlang.

As for leaky abstractions, I'd mitigate that by moving the lower-level algorithms into a separate module and limit the optimization pass to that module. Higher-level modules, like CLI entry points or API server route handlers, shouldn't need the extra optimization.

@miki I hope that #mojolang will push the #python community to put more effort into the performance of CPython. 3.13 probably is an indicator of that. I mean, suddenly GIL is optional and then there is a new JIT compiler as well.

In the end I believe Mojo will become Python 4.0 given that Modular does as they've said and go open source. But I believe it's a very low risk that they'll do so. Then they will just lose to the standard "interpreter" which should have incorporated much of the same.

@rmanos Yeah, I'm starting to rethink this. Golang certainly is what I'm looking for. What I (my personality) need is a language that is easy to read and that helps me to focus on the problem rather than the language and pattern.

Still, I'm considering this strategy:

Use Python as much as possible and use extension modules when necessary. Switch to #mojolang when the language is mature. Use #ziglang if I need to dig into low level stuff that can't be handled by Mojo (shouldn't happen really).