Code Models

The article might not make sense without some context.<p>This is part of &quot;Project Babylon&quot; and its mission is to: &quot;extend the reach of Java to foreign programming models such as SQL, differentiable programming, machine learning models, and GPUs. Babylon will achieve this with an enhancement to reflective programming in Java, called code reflection.&quot;<p>See: <a href="https:&#x2F;&#x2F;openjdk.org&#x2F;projects&#x2F;babylon&#x2F;" rel="nofollow">https:&#x2F;&#x2F;openjdk.org&#x2F;projects&#x2F;babylon&#x2F;</a>

Oh: Automatic differentiation of Java code using Code Reflection: <a href="https:&#x2F;&#x2F;openjdk.org&#x2F;projects&#x2F;babylon&#x2F;articles&#x2F;auto-diff" rel="nofollow">https:&#x2F;&#x2F;openjdk.org&#x2F;projects&#x2F;babylon&#x2F;articles&#x2F;auto-diff</a><p>This sounds interesting.<p>I remember that Swift for TensorFlow was similar.<p>Maybe you could also consider JAX to be similar.<p>Basically, can you do now sth similar as JAX but for Java? The article also talks about &quot;the Babylon GPU work requires the transformation of code models to GPU kernels&quot;.

It sounds cool but also like a remarkable level of scope creep for the JVM. I realize that Java ecosystem is far beyond simple these days. Nobody is spinning up a JVM implementation as a hobby project. But sad to see the deep entrenchment that is caused when an open standards platform is made so inconceivably complex that there is simply no opportunity to innovate on alternative implementations.<p>This is not an observation about this specific project, just about the organizational pressure to extend standards based systems beyond their core functionality, into territory where only few players can afford to roam.

This looks like it&#x27;s building on top of this prior JEP <a href="https:&#x2F;&#x2F;openjdk.org&#x2F;jeps&#x2F;457" rel="nofollow">https:&#x2F;&#x2F;openjdk.org&#x2F;jeps&#x2F;457</a>.

It looks complicated.<p>Here is my technique.<p>Trace the control flow and regenerate the flow on target programming language.<p>In their&#x27;s they have abstracted problem such as blocks and operation. But adding more condition to the philosophy is hard thing. The core principle needs simple

Is this a runtime MIR?

Oh great, the one way to make reflection even more unpredictable than it already is...<p>So instead of &quot;only&quot; finding that my choice of method names, class structure and presence or absence of ostensibly unused class members can change programs behaviour in arbitrary ways, now that property will extend to the implementation code itself?<p>Have fun getting reliable static analysis working on this stuff...

reminder: switch to openjdk if you haven&#x27;t already<p><a href="https:&#x2F;&#x2F;www.theregister.com&#x2F;2024&#x2F;06&#x2F;20&#x2F;oracle_java_licence_teams&#x2F;" rel="nofollow">https:&#x2F;&#x2F;www.theregister.com&#x2F;2024&#x2F;06&#x2F;20&#x2F;oracle_java_licence_t...</a>