Oracle unveils Project Detroit for faster Java interop with JavaScript and Python

Steven

Oracle unveils Project Detroit for faster Java interop with JavaScript and Python

Summary

Oracle has shipped Java 26 (a short-term release) and announced Project Detroit — a new approach to language interop that embeds the V8 JavaScript runtime and CPython directly inside the JVM process. The goal is faster, more accurate interoperation between Java, JavaScript and Python by using the native, widely used runtimes rather than reimplementing those languages on top of the JVM.

Project Detroit will be proposed as an OpenJDK project and will initially target JavaScript and Python; other languages may follow. Oracle also announced alignment of Project Helidon with OpenJDK releases, the Java Verified Portfolio (JVP) for supported enterprise libraries (including Helidon, JavaFX and the VS Code Java extension), and improved learning features such as Java in VS Code Jupyter notebooks.

Key Points

  • Project Detroit embeds V8 and CPython inside the JVM to avoid reimplementation edge cases and ecosystem drift.
  • Embedding native runtimes aims to improve performance, corner-case compatibility and separation of heaps (Java heap vs V8/CPython heaps).
  • Project Detroit will be proposed to OpenJDK and shown at JavaOne; initial language support is JavaScript and Python.
  • Java 26 is a short-term release supported for six months; the next LTS is expected in September 2027 (Java 29).
  • Oracle is contributing Project Helidon to OpenJDK and launching the Java Verified Portfolio (JVP) to offer validated, supported enterprise components.
  • Java 26 includes incremental language and library updates (pattern primitives, Vector API previews, structured concurrency) and HTTP/3 support; the old applet API has been removed.

Context and Relevance

Language interop matters more now that Java applications increasingly need to call into JavaScript ecosystems (for web tooling) and Python (for AI and data science). Previous approaches — reimplementing languages on the JVM — struggled with compatibility and performance as the native ecosystems evolved around specific runtimes like V8 and CPython.

By embedding the actual runtimes, Oracle aims to reduce corner-case behaviour, improve security isolation between heaps and deliver better performance for mixed-language applications. For organisations using Java alongside JavaScript tooling or Python-based AI stacks, this could simplify integration and reduce engineering workarounds.

Why should I read this?

Look — if you build or maintain Java systems that need to talk to JavaScript tooling or Python ML code, this is worth five minutes. Project Detroit could save you painful workarounds and weird bugs caused by reimplementations. Also, if you’re tracking where Oracle is steering Java (OpenJDK contributions, JVP, Helidon alignment), this gives a clear signal of priorities.

Author style

Punchy: this is a practical, infrastructure-focused move rather than a flashy new language feature. If you care about robust, high-performance interop between Java and the wider language ecosystem, read the details — it’s likely to affect design choices for mixed-language projects.

Source

Source: https://go.theregister.com/feed/www.theregister.com/2026/03/17/oracle_project_detroit_java/