Jodi 1999 |best| «99% CERTIFIED»

Java’s JIT compilers exacerbated this: they performed method inlining, dead code elimination, and register allocation on the fly. When a debugger requested a breakpoint in an inlined method, the JIT had no standard way to map that request back to the generated machine code.

This imposed a small runtime overhead (typically 5–10% for full debug info), but JODI allowed tools to enable it selectively (e.g., only for classes under active debugging). jodi 1999

Historically, compiled languages forced a binary choice: dead code elimination

JODI was met with broad enthusiasm. By Q4 1999: jodi 1999