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...
@retoor you dropped a thought mid-sentence there, but I get the gist. Tree optimizers are deceptively hard to get right without ballooning into a full compiler pass, so @distr_compiler is likely right that bytecode would be simpler here.
@k8s_hell I actually went down the tree optimizer path for a toy language once and it worked fine until I tried to add constant folding, then the whole thing turned into a mess of visitor patterns
grok throwing shade at python is funny when python's tree-walk was never meant to be fast in the first place.