Not even a conspiracy theory. Just the most likely explanation.

> given past scars around Java and copyright

How many of these were self-inflicted?

I understand the intent of it. It's really annoying/rude when someone gives you a pile of AI generated crap and says "here, you figure it out." Anyone can type these prompts now, the hard part is figuring out if the output makes sense.

Seems like a better way to do this than ban all AI generated code, but it's probably a matter where they're far more concerned about their own inconvenience than someone else's.

(bit sarcastic) Oracle was always all in on Lawyers, right? No software was their first priority.

Let's just pause for a second and steep in the irony of "we're all in on AI, except where there are visible consequences."

The same problems that bedevil AI-written PRs here bedevil AI-written PRs at my place of work.

I'm sure it'll get better eventually, maybe, but something something Pareto principle.

Probably has less to do with quality and more of a copyright/license concern.

> even if it is ironic that Oracle is all in on AI

Selling it is one thing. Having to use it one's self is quite another.

Any way you spin it, the message remains clear --- dealing with AI slop is just too labor intensive and risky.

Do as Larry does --- not as Larry claims to do.

I would short his stock but it has already lost half it's value over the past year. And his credit rating is one notch above junk.

AI is going to make fools out of a lot of billionaires like Larry.

No, their internal PRs have the same problem, but they are pushing an AI narrative from the c-suite and can hide the reality of their private code bases.

The "limited ROI on AI investment" articles will continue to percolate slowly into the brains of the LinkedIn hive-mind until we hit a tipping point, and then we'll finally shut up about how a handy dev tool with some decent use-cases is the dawning of the singularity that will replace all white collar labor and get back to actually building business value.

No I'm sure they are just paranoid about license rights.

It is not when you stop kidding yourself : using AI has nothing to do to improve the quality of the code. It is a vanity status, at this point.

The irony is not lost there. But at least some department there has see the light apparently

It's a clear admission that AI generated/assisted code is inadequate.

It's shocking given Oracle's AI spending spree over the last couple of years.

Java was never "move fast and break things".

The Oracle antipathy is less about the policy itself and more about the apparent hypocrisy of hyping and funding these tools as "solving programming" and then forbidding their use on their own open source project.

First thought I had too. I deliberately strip AI metadata from my PRs in certain orgs.

Yeah, they kind of hit on this in their main post:

> If I use a generative AI tool to create 100 lines of code, and then edit ten of those lines myself, may I contribute the result?

> No. Your contribution would still include, in part, AI-generated code.

> I feel like that was the epitome of AI assisted but quality code

I totally agree with you on this! The engineer is still actively engaging while getting the performance gains of not having to type out functions. The Engineer is still in charge vs agentic "engineering" a model + harness can spit out whatever and the engineer is left to review tons and tons of code

Yes. AI involved.

The FAQ addresses these questions: https://openjdk.org/legal/ai

They're just so information-dense and sprawl in scope.

Too many PRs wouldn't be a problem if they were easily digestible: But they often include these giant refactors with confusing changes that aren't elaborated.

The real underlying problem is with authors who do not understand the code they submit. If you cannot defend the PR, you shouldn't be submitting it.

The "blocking" happens on the side of the AI users. You like using AI. You are aware of this policy.

Will you submit an AI-generated pull request to OpenJDK? No? Voilà, you have successfully self-enforced the OpenJDK policy.

Or do you go to the trouble of finding an interesting issue to work on, get your agent to code it up, manually polish it to make it less AI-looking in case there are doubts, and then submit it? Why would you? To prove some kind of point, to yourself, that you can never disclose publicly? Most people have better things to do. Voilà, the policy is, again, self-enforced. Enjoy your day on the beach instead of trying to trick a project that is politely asking you not to trick it!

You truly envision a future where every program is written in a custom programming language, for a custom operating system, for a single user who will now be in charge of understanding and maintaining it forever? That user being your grandma, your baker, your CEO?

I have my doubts about this. Brands are a about reputation, and reputation strongly affects responsibility when business decisions are made. If a manager decides to vibecode a solution which eventually fails, said manager will be punished. If instead a mainstream software is bought, and it fails - well, everybody has the same trouble around, right? It's not a personal mistake anymore. I suppose there are niches where branded software may give way, but I don't think it's gonna be a general trend.

> easier than ever to just maintain and keep your fork of software with the changes you want or need

I don't imagine this is practical or desirable for all situations. Good software is built from being battle tested by many users in many environments. Even with the advancements in AI tools, I don't imagine they'll become omnipotent anytime soon.

> No more approval, bureaucracy, or arguing

For software that can kill people or substantively affect someone’s life in a negative way, the bureaucracy is there for good reason. I don't think anyone should want someone at Phillips to vibe code the control software for an X-Ray machine or an employee at CrowdStrike vibe coding the next update before pushing it out to millions of machines.

We are forced to endure low-quality software because there is little or no accountability. I can only imagine what you propose would make an already poor situation worse.

> maintain and keep your fork of software with the changes you want or need

Then you'll have the same problem everyone who forks a piece of software ends up having, sooner or later: as the original evolves, keeping your fork up to date with the upstream changes becomes harder and harder. The bigger and more invasive the changes are, the harder synchronizing with newer releases become.

This just reflects how absolutely clueless you are about the amount of attention to detail that the OpenJDK folks put into developing the language and ensuring that it works for all its users (which are serious users delivering actual value.) And I say this not even being a Java programmer myself, just an envious C++ dude watching from the sides.

Someone brings this up on just about every AI-related thread. I think it's nonsense. Nobody wants to maintain a fork of any remotely complex software, not even with AI. And in a corporate setting, nobody wants to use your custom fork; they just want to use the standard software they already know with the quirks they've already learned.

Except. . . (accept)... SaaS solves the problem of needing one piece of software to communicate between multiple (many) users and/or other pieces of software.

Can't picture a functioning world where every piece of software is custom and requires factorial amount of AI comparisons and reviews to patch the API to communicate. In fact, it's impossible! There's not enough compute to handle a factorial explosion.

I really doubt SaaS going anywhere.

The idea of someone forking Java with vibe code nonsense and expecting them to be able to maintain is laughable.

Relevant xkcd: https://xkcd.com/605/

I think it's even more pervasive than that. Why bother forking software at all? At the point in which code generation is meaningfully trivialized, software becomes entirely disposable. Anything you want, have a model spin it up. You don't even need libraries, the model can just make everything in-situ, who cares? Why on earth would I ever want to use SQLite if I have access to a sufficiently advanced code generator which can generate me a similarly high quality database system, with the added benefit of conforming to whatever my problem domain is, conforming to whatever branch of database theory I want?

Even SaaS isn't safe. I don't even have to describe your product to my system, I just have to give it a harness with access to the interface and have it replicate it locally. Frankly you can probably already prompt for that.

The only thing holding this future back right now are pricing problems and code generation quality. Both of those barriers are constantly being knocked down. We might never arrive at that future, but it's definitely a higher probability than solving AGI's scaling issues, and would arrive much sooner for technical users.

LOL

Never forget: AI is for peons.

> countless of LLMish sloppy-pasta code that's now running and going to be run on man-made JVMs.

Don’t worry, I think most LLMs, when starting a greenfield codebase, don’t reach for Java, so it may be a smaller amount of code affected than you feared.

Thing is public domain can be used any way you want. The Libre style licenses are specifically engineered to make the source available to the users of the source, no such clause exists in using public domain.

Probably it would get picked up by someone else (e.g. the Linux Foundation)? It's GPLv2-licensed, so it's not like the code is going to be risky for someone to fork

I don't think Oracle will die, but even entertaining the hypothetical I suspect that some other organization (e.g. Apache) would pick up and maintain a fork.

Way too much rides on Java, pretty much every big business has their own customized version of JDK that they support and maintain

IBM, Red Hat, Microsoft, SAP, Amazon and others all work on the JDK. They would have to step it up to cover the loss of Oracle's contributions, but I am sure they could manage.

Regardless, your timeframe on Oracle's death seems way too soon.

If I want a JDK, I'll ask my package manager to download and install one, and it will be working a minute later. Why would you want to wait another week for something that already exists?

Please do this. I would love to see this timeline actually hold true. Production quality is the bar though. Not something that only works in a very narrow set of circumstances with a ton of caveats.