It was poetry. The Python script ran inside the same memory space as her Swing UI. It was fast. It was clean. And it was all orchestrated from within NetBeans, with breakpoints that jumped from Java brackets to Python indents. On demo day, the sneaker-wearing CTO leaned over her shoulder. Her NetBeans project was open: a tidy tree of .java files and a folder of .py scripts, all color-coded, all under the same build system.
She rewrote the integration. Instead of launching python.exe , she wrote a tiny Java wrapper:
Then came Project Chimera.
The CTO’s jaw dropped. "You're debugging Python and Java… together ?"
Her eyes narrowed. For the next three days, Lena refused to use the process builder. She dove into the forgotten corners of the NetBeans plugin ecosystem. She discovered that NetBeans 12+ had a hidden gem: GraalVM Polyglot integration. If she configured her project to use GraalVM as the platform, she could run Python code natively on the JVM .
