FXyz VS JITWatch

"and then a 3D line from there to the 3D sphere. " No, this line segment is also a 2D line. Actually its two lines of different colors, thickness and transparency which gives the illusion of 3D shading. I have a manager which reacts to any camera position/rotation changes by computing a transform of the 3D position of the sphere to a 2D point. The line segment's start x and y are bound to that 2D point. An example of how to do that same dynamic transform but with labels is in FXyz3d: https://github.com/FXyz/FXyz/blob/master/FXyz-Samples/src/main/java/org/fxyz3d/samples/utilities/FloatingLabels.java

The CAD models are slightly simplified versions of our machining models and exported as OBJ. They are more complex and produce more artifacts than hand-crafted models, but with instance sharing it's no issue to display hundreds of actuators simultaneously. Most of the models are 1-10MB, but the Hexapod chassis at the end is an unmodified export with ~150MB. The models are loaded using the OBJ loader bundled with FXyz.

You can kind of do the same as DISASSEMBLE in Clojure.

There are some helper projects like https://github.com/Bronsa/tools.decompiler, and on the OpenJDK JitWatch (https://github.com/AdoptOpenJDK/jitwatch), other JVMs have similar tools as well.

It isn't as straightforward as in Lisp, but it is nonetheless doable.

As you have encapsulated the asserts inside methods, these will be called at runtime with the arguments evaluated (for example, creating that lambda). When assertions are disabled, the C1/C2 may inline the empty method call eventually, but I don't know whether it drops the lambda instantiation as well. You can use JITWatch to see what gets inlined. The general notion though is to not worry too much. Lazy log messages are a common pattern.

You can use jitwatch for this. To see the actual assembly code generated you will also need to use a debug build of the jvm.

If you use Oracle's own IDE, it will support it out of the box, as it already did on Sun's days.

Then there are other ways depending on which JVM implementation is used.

On OpenJDK's case you can load runtime plugin to do it

https://github.com/AdoptOpenJDK/jitwatch

We use https://github.com/AdoptOpenJDK/jitwatch for this.

If you already know any JVM or .NET language, the first step would be to understand the full stack, you don't need C for that.

Many of us were doing systems programming with other languages before C went mainstream.

What you need to learn is computer architecture.

Getting back to JVM or .NET, you can get hold of JIT Watch, VS debug mode or play online in SharpLab.

Get to understand how some code gets translated into MSIL/JVM, and how those bytecodes end up being converted into machine code.

https://github.com/AdoptOpenJDK/jitwatch/wiki/Screenshots

https://sharplab.io/

Languages like F# and C# allow you to leave the high level comfort and also do most of the stuff you would be doing in C.

Or just pick D, which provides the same comfort and goes even further in low level capabilities.

Use them to write a toy compiler, userspace driver, talking to GPIO pins in a PI, manipulating B-Tree data stuctures directly from inodes, a TCP/IP userspace driver.

Not advocating not to learn Zig, do it still, the more languages one learns the better.

Only advocating what might be an easier transition path into learning about systems programming concepts.

You can enable a lot of debug information about how the compiler decides what to do with your code using feature flags like -XX:+UnlockDiagnosticVMOptions -XX:+PrintInlining. If you want to dive deeper into the world of the Hotspot JIT Compiler, have a look at JITWatch.

In what concerns HotSpot, one way would be JITWatch.