Grok disses Python beyond recovery 😱

I am working on Rava2 (the second version of my Rava Java Interpreter). The difference is that the focus is on source code quality now, above performance. Rava1 had so many performance optimizations that it became a bit of a Frankenstein. That didn’t feel good. 😕

Now, I let Grok give opinions about what to work on, based on benchmark results (the benchmark is like 15 different tests executed by Python, Rava2, and Java). And Grok decided to diss Python like never before:

Rava2 is now beating Python on a solid majority of these benchmarks, which is a big win compared to the early tables. However, the performance is still far from where it needs to be for a serious language.

Sure, it beats Python, but is not a serious language yet 😛

I have some very nice implementations in mind to optimize even further. I want to keep it a tree-walk interpreter - which is not very known for performance. I don’t want bytecode. I’m considering designing a tree optimizer. I have to think it through. But I think it’s possible to make it blazing fast.

So far, I did not let it implement JIT because it’s too complex in many cases for me. I should learn more about that before I implement it. It’s important to understand what is happening. I don’t want to win the performance game at all costs.