She rewrote the integration. Instead of launching python.exe , she wrote a tiny Java wrapper:
The CTO’s jaw dropped. "You're debugging Python and Java… together ?" python for netbeans
Lena Vasquez was a creature of habit. For eight years, her world had been Java, Maven, and the comforting, orange-tinted glow of Apache NetBeans. Her coworkers mocked her loyalty. "IntelliJ is smarter," they said. "VS Code is the future," they chanted. But Lena loved NetBeans the way a carpenter loves a well-worn hammer. It was predictable, powerful, and never asked her to pay for a subscription. She rewrote the integration
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 . For eight years, her world had been Java,
"Side by side," Lena said, stepping through the code. "The JVM doesn't care what language you speak. And NetBeans? It just wants to help you build." That story became legend in her company. The "NetBeans Necromancer," they called her—the one who resurrected a dead IDE with bleeding-edge polyglot magic.