The Java community spent this week arguing about the OpenJDK interim policy on AI-generated code, and the policy's own FAQ explains the real reason it exists. "Generative AI tools, by their nature, make it easy to create large quantities of plausible-looking code, with plausible-looking tests, which is nonetheless incorrect," it says. "Reviewing submissions of such code can easily become a drain on the already limited time of human reviewers."
That is the whole argument in one sentence: AI output is cheap, and reviewing it is expensive. The policy bans content "generated, in part or in full, by large language models, diffusion models, or similar deep-learning systems" from OpenJDK repositories, pull requests, email, wiki pages, and JBS issues. The thread on Hacker News is at 396 points and 266 comments, and most of the heat comes from the contrast with Oracle's own position. Larry Ellison told Oracle AI World 2025: "The code that Oracle is writing, Oracle isn't writing. Our AI models are writing." Meanwhile Oracle cut 21,000 jobs in June citing AI deployment and is borrowing tens of billions for AI datacenters, as The Register laid out.
AI code is fine inside Oracle. AI code is not fine in the JDK. The difference is the review burden, the thing nobody wants to scale.
