Oracle bans AI-generated code from OpenJDK

Oracle has dropped a no AI-written code rule on OpenJDK, the open-source project behind a huge amount of the world’s Java software, and the internet immediately went into "wait, what?" mode. The official reason is serious stuff: safety, security, and possible legal trouble over who really owns machine-generated work. Developers can still use chatbots and coding assistants in private to help check or debug things, but they can’t paste that AI output into public contributions. In plain English: think with the bot if you want, just don’t turn in the bot’s homework.

The comments, though, were where the real fireworks started. One camp basically said, good—Java already runs banks, businesses, and boring-but-important real-world systems just fine without what one commenter mockingly called “LLMish sloppy-pasta.” Another camp zeroed in on the awkward optics: Oracle’s leaders have been loudly bragging that AI helps write Oracle’s own code, so banning it from the public-facing project struck people as peak “rules for thee, not for me.” Several commenters openly called it weird, ironic, and maybe a sign Oracle is nervous about future lawsuits.

Then came the jokes. People wondered whether handy tools like Cursor’s autocomplete now count as forbidden robot help, while others fantasized about a legal apocalypse where companies would have to rip AI-made code back out of their products. Add Oracle’s $70 billion spending binge on AI-ready data centers—and a credit downgrade hovering just above junk status—and commenters saw a company going all-in on AI with one hand while slapping it away with the other. Delicious contradiction? The crowd certainly thought so.