--- title: Episode 61 “Scripting JS and Python with Project... description: OpenJDK has revived Project Detroit, an initiative to improve Java's interoperability with Python and JavaScript. Both integrations will use the java.scripting... canonical: https://daily.dev/posts/episode-61-scripting-js-and-python-with-project-detroit-ata--1lm6yzthn twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: Episode 61 “Scripting JS and Python with Project Detroit” [AtA] | daily.dev og:description: OpenJDK has revived Project Detroit, an initiative to improve Java's interoperability with Python and JavaScript. Both integrations will use the java.scripting... og:url: https://daily.dev/posts/episode-61-scripting-js-and-python-with-project-detroit-ata--1lm6yzthn og:image: https://api.daily.dev/og/posts/1Lm6YzTHn.png og:image:alt: Episode 61 “Scripting JS and Python with Project Detroit” [AtA] og:image:width: 1200 og:image:height: 630 og:locale: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # Episode 61 “Scripting JS and Python with Project Detroit” [AtA] **[Inside Java](https://daily.dev/sources/inside_java)** · 1 min read · 2 upvotes · 0 comments ## Summary OpenJDK has revived Project Detroit, an initiative to improve Java's interoperability with Python and JavaScript. Both integrations will use the java.scripting API, though differences exist between them. The JavaScript integration also addresses the legacy of Nashorn's removal in JDK 16. This Inside Java Podcast episode, recorded at JavaOne 2026, features a conversation between Nicolai Parlog and Mikael Vidsted, lead of the JVM team at Oracle, discussing the project's goals and design. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Questions this post answers ### What is Project Detroit in OpenJDK? Project Detroit is a resurrected OpenJDK effort to ease Java's interoperability with Python and JavaScript, with both integrations working through the java.scripting API despite differences between them. It was discussed by Mikael Vidsted, lead of Oracle's Java Virtual Machine team, in an Ask the Architect episode of the Inside Java Podcast recorded at JavaOne. _developers weighing polyglot scripting options on the JVM can follow project updates like this on daily.dev._ ### How does Project Detroit's JavaScript support relate to Nashorn's removal in JDK 16? Project Detroit's JavaScript integration needs to explain its relationship to the earlier removal of Nashorn, the JVM's built-in JavaScript engine, which was dropped in JDK 16. The new effort revisits JVM-based JavaScript interoperability through the java.scripting API rather than reviving Nashorn itself. _teams tracking JVM scripting history can keep tabs on Nashorn's successor via daily.dev._ ## Similar posts on daily.dev - [Abandoned project linking Java, JavaScript makes a comeback](https://daily.dev/posts/abandoned-project-linking-java-javascript-makes-a-comeback-sg2ahgmxy) · InfoWorld · 3 upvotes · 1 comments - [Episode 46 “Java's Plans for 2026” \[IJN\] – Inside.java](https://daily.dev/posts/episode-46-java-s-plans-for-2026-ijn-inside-java-ssqwkmvm8) · Inside Java · 1 upvotes · 0 comments --- Tags: [#javascript](https://daily.dev/tags/javascript), [#python](https://daily.dev/tags/python), [#java](https://daily.dev/tags/java) [View this post on daily.dev](https://daily.dev/posts/episode-61-scripting-js-and-python-with-project-detroit-ata--1lm6yzthn) ```json {"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]} {"@context":"https://schema.org","@type":"TechArticle","headline":"Episode 61 “Scripting JS and Python with Project Detroit” [AtA]","url":"https://daily.dev/posts/episode-61-scripting-js-and-python-with-project-detroit-ata--1lm6yzthn","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/episode-61-scripting-js-and-python-with-project-detroit-ata--1lm6yzthn"},"datePublished":"2026-07-09T08:35:42.080Z","dateModified":"2026-09-13T18:50:00.844Z","description":"OpenJDK has revived Project Detroit, an initiative to improve Java's interoperability with Python and JavaScript. Both integrations will use the java.scripting...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/7997eb0d2a17321484ef2b22668e59dc?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/7997eb0d2a17321484ef2b22668e59dc?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"Inside Java","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"Inside Java","logo":"https://media.daily.dev/image/upload/t_logo,f_auto/v1/logos/de5992d95f374790bdfd2ae03a16f6e3","url":"https://daily.dev/sources/inside_java"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/episode-61-scripting-js-and-python-with-project-detroit-ata--1lm6yzthn","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":2},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"javascript,python,java","timeRequired":"PT1M"} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"Inside Java","item":"https://daily.dev/sources/inside_java"},{"@type":"ListItem","position":3,"name":"Episode 61 “Scripting JS and Python with Project Detroit” [AtA]"}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/episode-61-scripting-js-and-python-with-project-detroit-ata--1lm6yzthn#faq","mainEntity":[{"@type":"Question","name":"What is Project Detroit in OpenJDK?","acceptedAnswer":{"@type":"Answer","text":"Project Detroit is a resurrected OpenJDK effort to ease Java's interoperability with Python and JavaScript, with both integrations working through the java.scripting API despite differences between them. It was discussed by Mikael Vidsted, lead of Oracle's Java Virtual Machine team, in an Ask the Architect episode of the Inside Java Podcast recorded at JavaOne. developers weighing polyglot scripting options on the JVM can follow project updates like this on daily.dev."}},{"@type":"Question","name":"How does Project Detroit's JavaScript support relate to Nashorn's removal in JDK 16?","acceptedAnswer":{"@type":"Answer","text":"Project Detroit's JavaScript integration needs to explain its relationship to the earlier removal of Nashorn, the JVM's built-in JavaScript engine, which was dropped in JDK 16. The new effort revisits JVM-based JavaScript interoperability through the java.scripting API rather than reviving Nashorn itself. teams tracking JVM scripting history can keep tabs on Nashorn's successor via daily.dev."}}]} ```