[crux_]

I don't think it has much to do with human-readability; but rather with:

- automatically finding and applying optimizations

- with a general approach, rather than a big database of hard-coded optimizations.

I'm not sure how (or how well) it all works, though... but it's the sort of thing I find interesting, so here's hoping for some free time sooner or later. ;)

[gte910h]

If it's "yet another thing I run after I am done writing code" that's just a optimizer IMO, not a different sort of thing.

If it actually changes the code I have written, and then leaves it in that state for some reason 1> I want to know about that and 2> I want to know about if the trade offs of using it are worth it for the payments we make via reduced readability and malleability.

[crux_]

It's a component for your compiler, not something that would likely exist in a standalone form except for demonstration & research.

(For the purposes of above comment, JIT interpreters absolutely count as compilers.)

And yes, it's 'just' an optimizer. It so happens to be a fairly interesting approach.