Oracle, the law firm with a tech business attached, probably wants to retain the option to sue other people for AI-washing their proprietary code, and that doesn't work if they're also publicly accepting AI contributions to their code with no apparent concern for the provenance of it. The tech business would probably tell them this isn't going to be a needle they are going to be able to successfully thread, but the law firm is in the driver's seat.
What I don't understand is why anyone with half a brain would even venture to touch Oracle with a ten foot pole given that they've had this reputation for at least the last 25 years.
The same reason why most huge enterprises buy insane support contracts for every other piece of shitty software: support, and someone to blame when production goes pear-shaped. Because there’s no real management left anywhere, there’s no time to grow expertise internally and everyone just needs that hit of Risk Management (tm), they’ll go to whatever lengths to get it. Oracle is like the ultimate warm, fuzzy blanket where that fuzz is actually mold, to the scared-shitless enterprises of having to think for themselves.
"Do not fall into the trap of anthropomorphizing Larry Ellison. You need to think of Larry Ellison the way you think of a lawnmower. You don't anthropomorphize your lawnmower, the lawnmower just mows the lawn - you stick your hand in there and it'll chop it off, the end. You don't think 'oh, the lawnmower hates me' - lawnmower doesn't give a * about you, the lawnmower can't hate you. Don't anthropomorphize the lawnmower. Don't fall into that trap about Oracle." --Bryan Cantrill
What about a guy with a lawnmower intentionally chopping off your foot? And what about a CEO making decisions on behalf of the corporate entity called Oracle?
It doesn't matter if the lawnmower is chopping off feat intentionally or not. If it's presenting a public hazard, it should be stopped. Even though the ocean couldn't care less it doesn't prevent us from building breakwalls. And Larry Ellison isn't unstoppable as the ocean.
Rather than harmless, what the lawnmower analogy achieves is to make him seem blameless. "How can you assign blame to a thing that's just doing what it's built to do without any intent?" It's important to push back against that. Intent isn't a necessary condition for something to be dangerous, and so it's not necessary to ask whether it is intentional or not. A rabid dog will be put down regardless of who is to blame for it.
I think the point of the lawnmower analogy is to subjectively characterize Larry Ellison and Oracle from the viewpoint of someone who has had the unfortunate experience of having to deal personally with either of them in some way. You feel powerless against the machine, as it were, and the best course of action is to keep yourself far from the blade.
I think you both are missing the point. Hes sayin larry is inhuman, hes closer to an apex predator or a serial killer freak of nature than your ordinary human
We're not missing the point, we simply don't agree. You're putting him too much on a pedestal. He's an ordinary human bound by the same laws anyone else. If he's criminally insane and can't be held accountable for his actions, he should be locked up in an mental institution, not running a corporation.
Don not fall into the trap of anthropomorphizing Larry Ellison. You need to think of Larry Ellison the way you think of a 1958 Plymouth Fury named Christine. You don't anthropomorphize your killer car, the killer car is just out for blood - you rebuild it and it kills your friends and family, the end. You don't think 'oh, Christine hates me' - Christine doesn't give a * about you, Christine can't hate you. Don't anthropomorphize a 1958 Plymouth Fury named Christine. Don't fall into that trap about Oracle.
Never thought to hear someone here mention Maximum Overdrive. Indeed a hilarious movie and the only movie for which AC/DC ever recorded an (instrumental) soundtrack.
The flaw in the analogy is that oracle is made of people. It's not a lawnmower, it's a group of people with human motivations and human thoughts. It's true they don't HATE people, but it's also true they absolutely have no conscience in negotiations and have zero concern about relationships.
Maybe so, but perhaps the most successful part of the AI marketing pitch has been exploiting management's hatred of labor (and vice versa).
A significant motivator for a lot of the nonsensical AI layoffs and initiatives over the last three years has been that it's a great opportunity for management to get ill on their slaves.
Tech labor got a little too big for their britches during the hiring spree of 2021, and AI was a great opportunity to take them down a peg, even if it offered little in the way of ROI.
He's talking about the owner of Oracle, not the people who work there. It doesn't matter how many smart and talented real humans work at Oracle, the guy running it acts like a fleshy paperclip optimizer.
How many bureaucracies in history have behaved in deeply misanthropic ways, especially when led by misanthropic leaders?
Don't underestimate the power of the desire to keep one's job to cause a large organization to behave towards its own self-perpetuation despite the moral lines that must be crossed by individuals to do so.
> How many bureaucracies in history have behaved in deeply misanthropic ways, especially when led by misanthropic leaders?
Lots!
> Don't underestimate the power of the desire to keep one's job to cause a large organization to behave towards its own self-perpetuation despite the moral lines that must be crossed by individuals to do so.
For reference, Walter Lippmann is the guy from the NYT who covered up the Holodomor in Ukraine (1930s) in the west as well as Stalin's gulags and purges. I wouldn't call him the voice of the proletariat in any way. He was the voice of the Stalinist in the west and the term tankie was invented for him and people like him.
That’s an interesting story to bring up in this context, because I have always wondered how a fundamentally customer-hostile business like Oracle could be so successful. It really puts the lie to libertarian cliches about the invisible hand of capitalism that ends up being philanthropic in spite of itself.
I think free society in general absolutely requires its people to be generally moral and civil. Freedom inevitably evaporates as morality and civility decline.
And that's why it's important to go after morally corrupt, uncivil monsters.
The problem today is that the press and the DAs/courts are complicit--they're less interested than ever in pursuing public morality and civility as ends in themselves. They're mostly only interested in partisan politics.
The lawnmower exists, you might disagree, but it’s not your lawnmower, you can’t uncreate it. But you can and should take care never to put your hand near it.
Well (to make an analogy), nature produces psychopaths - some people's brains just aren't capable of empathy. Whether you characterize that observation as "legitimizing" or just "being realistic" is merely a philosophical concern.
What I meant was that there is no moralizing of natural force, which this metaphor tries to equivocate. Oh, it's just like the wind, don't get in Larry's way!
It’s been established that LLM-generated code is not copyrighted so I can fully understand the company living from copyrighted data to not accept LLM-generated contributions.
> It’s been established that LLM-generated code is not copyrighted
If that's a reference to Thaler v. Perlmutter, the only thing that's been established is that an LLM can't be considered an author under the Copyright Act, only a human being can. It says nothing about the consequences of a human claiming authorship of LLM-generated code, which would be relevant here.
My understanding (belief) is that it's going to depend on how much human involvement is there.
If you write a prompt and one-shot a problem and share the source code, that source code is probably not covered by copyright.
If you substantially edit or modify the generated code you would own the copyright.
It's like with a camera. If I set a camera and carefully aim it and somehow trigger the shutter then make adjustments in Photoshop, I own the copyright on that image.
If I stick a Flock camera on a pole somewhere and post the live output, there's been no meaningful human creative involvement in producing those images and so nobody can claim copyright on them.
I think if I as a human use an llm to do something technical that would qualify copyright, it should still qualify for copyright. How do you decide how much human is copyrightable. If I use a package that writes code or use a library for some piece of it, I could still copyright.
I don't like this idea that llm code can't be owned by a human, copyrighted. It's just code.
I think your last example with flock camera is relevant here - I can take a picture of a public football as a reporter or something (or a fan I guess) and I can copyright and sell that picture. Newspapers do it every day.
So if I stand on a street corner and take a pic, it's copyrightable. If I take a pic using a flock camera it should also be copyrightable, just like if my nest camera at home takes a pic of something, I can use that.
I guess you are saying "someone else owns the flock camera" so you don't get to own pictures. What if I buy the flock-like camera and put it up, I should own that.
You seem to have misunderstood an is/ought distinction. You may hold the (fairly extreme, as far as copyright goes) position that surveillance footage should be subject to copyright, but it's well established that it's not. Who owns the camera is irrelevant. At least in the US; I'm not aware of any jurisdictions that hold otherwise. This is why Wikipedia articles on world events in the past few decades are full of stills from surveillance cameras: it's one of the few sources of imagery of an event that are unambiguously legal to include, because unlike a photo or intentionally made video of something specific, it's not a creative work. It's also pretty firmly established that human authorship is required for something to be subject to copyright, and having an idea that lead to some particular expression is itself not sufficient; see, e.g.: https://en.wikipedia.org/wiki/Monkey_selfie_copyright_disput...
I appreciate your informed take. I follow the reasoning but I am amazed it works this way. I found some articles that supported what you said, and also said there's a follow-on industry that figured out how to alter and edit videos just enough for a revised video to have creative contribution and make it copyrightable.
This is a great case to study, but no determination of copyright was made. The only actual lawsuit was filed by PETA arguing that the monkey should have copyright, which led to a settlement with the human photographer and nothing else because obviously that's not possible.
For various reasons (mostly $$$) the guy never actually got a judgement. I think the chances are good that he could have prevailed in court; there is significant creative input to setting up cameras and triggers in a way to convince a wild monkey to take a selfie. It's not like he just left his camera sitting somewhere on accident and came back to find a photo in it.
I'm also not a lawyer, but I did do a lot of work in copyright for a company you've heard about.
> If you write a prompt and one-shot a problem and share the source code, that source code is probably not covered by copyright.
We will have to see about that! This is the kind of boundary that's still being figured out in court; it's going to depend on how hard you worked on the prompt. I highly doubt that even most slop was generated with a single half-ass prompt, and the bar is not as high as you might expect.
> If I stick a Flock camera on a pole somewhere and post the live output, there's been no meaningful human creative involvement in producing those images and so nobody can claim copyright on them.
It really depends on what pole, where, and why. In a parking lot in rural Wisconsin? Probably not. A recorded livestream of a political march? You likely have copyright.
I think that by virtue of the sheer amount of time spent using AI tools, it's pretty clear that these outputs have enough creative input to be copyrightable.
No, that’s not what they are saying. They’re saying that the code generated by a human with help from an LLM may potentially be. This is what I hope we are going to arrive at, eventually.
How could you establish what parts of the code was produced by an LLM vs updated by a human afterwards?
The LLM will output different results over time as the models get updated. Are we heading towards needing to retain a full prompt history that can be replayed against a specific LLM model version to prove what the output was for copyright purposes?
For those wondering what the difference is: consider what happens when an LLM regurgitates its training data. It's copyrighted... but not by the person who generated it.
This is a false narrative based on a (IMO often intentional) misunderstanding. It has by no means been established by any court that LLM-generated code is not copyrightable.
Thaler v. Perlmutter stands for a much narrower proposition and at any rate is not binding nationally, SCOTUS having denied certiorari.
This is not necessarily true. While no court has explicitly come out and said that copyright does not apply to AI-generated works of authorship, the US copyright office has[0]:
> Based on an analysis of copyright law and policy, informed by the many thoughtful comments in response to our NOI, the Office makes the following conclusions and recommendations:
> • Questions of copyrightability and AI can be resolved pursuant to existing law, without the need for legislative change.
> • The use of AI tools to assist rather than stand in for human creativity does not affect the availability of copyright protection for the output.
> • Copyright protects the original expression in a work created by a human author, even if the work also includes AI-generated material.
> • Copyright does not extend to purely AI-generated material, or material where there is insufficient human control over the expressive elements.
> • Whether human contributions to AI-generated outputs are sufficient to constitute authorship must be analyzed on a case-by-case basis.
> • Based on the functioning of current generally available technology, prompts do not alone provide sufficient control.
> • Human authors are entitled to copyright in their works of authorship that are perceptible in AI-generated outputs, as well as the creative selection, coordination, or arrangement of material in the outputs, or creative modifications of the outputs.
> • The case has not been made for additional copyright or sui generis protection for AI-generated content.
> The Office will continue to monitor technological and legal developments to determine whether any of these conclusions should be revisited. It will also provide ongoing assistance to the public, including through additional registration guidance and an update to the Compendium of U.S. Copyright Office Practices.
Congress or the courts could, of course, override the stance of the copyright office, but I think it would be highly unusual for them to do so (particularly for something like this). It would however be a lot better if congress just stepped in and said no outright, but until then this will have to do.
Do you own the copyright to a painting you commissioned or does the artist? You may have described what you wanted, but the creative work is the output of the artist. Same with an LLM.
Sure, but I would be incredibly shocked if the courts overturned these conclusions. These kinds of determinations are within the remit of the USCO, so a court does not need to come out and say it if the USCO has already done so. Obviously, as I said it would be better if congress weighed in and solved this problem, given that the USCO is free to publish a new NOI to change it's practices/policies, but we all know that congress is too gridlocked atm for that to happen
I am trying really hard not to accuse you of not having read what you posted, because your conclusions are in strong tension with what it plainly says.
> Whether human contributions to AI-generated outputs are sufficient to constitute authorship must be analyzed on a case-by-case basis
It says a plain prompt is not enough but that is not the reality of real software development. People aren't one-shotting complex business apps. The vast majority of software development will trivially pass that bar and end up in the "requires case by case analysis".
You are a false narrative. I’m just repeating what I read. The thing is, it’s murky waters. Someone’s going to challenge it but do you want to be the guy who takes it on a chin?
The sibling comment lays this out and my original comment above is based on exactly the same link.
Also it's a different story intranationally for those of us who live in countries with much more restrictive/no fair use. Are you geolocking your software to the USA?
I highly doubt that that's the last word on that matter, but even if: Even before LLMs you could combine individual non-copyrighted components into something copyrighted.
Legal departments are ironically very much like LLMs.
They are trained on a narrow set of data and don't really understand the real world.
If you let them run wild with no supervision they'll turn your company into slop.
Someone needs to be there to reign them in, asking the all-important questions like "is suing all of our customers and making them angry REALLY the best option?" (to which they will reply, "You're right to push back on this").
This is typically the role of the CEO, however, as we know, most CEOs of large successful companies are too busy to actually do that. They're mostly training Brazilian Jiu Jitsu, shitposting on their own social media platform, trying to manipulate international politics, or helping run their family nonprofit.
This is why I believe that legal departments need to be demoted. The legal department should not report to the CEO, they should report to a new role that is above both PR and legal. And that person's job should be to force legal and public relations (which we know are natural enemies) to work together. Every press release goes through legal now, and it's only logical that ever legal action should go through public relations review as well.
The fact that public relations at most large companies has atrophied from disuse in our public-equity-owned unicorporate cooperation-over-competition chaebol/zaibatsu/conglomerate world is a problem for another day.
Disclaimer: I use AI at work and for some projects at home and find it really useful (as long as you know when and how to use it)
With that said... It's funny how we went from "vibe coding" to review burden, sloppy contributions, copyright issues, unclear ownership (as in: who will fix bugs), needlessly verbose code, etc, etc. Several projects have banned AI contributions now and counting.
As I said, I use AI to help architect and write code and really like it; still, I cannot even count the times anymore where the model (we use multiple of the frontier ones) has completely gone down the primrose path.
I always make sure I make it my code, every line is reviewed and understood, maybe I rewrite the AI output here and there, I understand the tests and testing strategy, etc, etc.
So I wonder where this is all going. We are past "vibe" coding already, and so far monetization of AI has been "patchy". On top of that local AI is becoming more and more viable.
I guess that depends on whether you think the motivations matter. When it comes to a policy on a hot-button issue that seems like it could easily be enforced selectively, I don't think it's a stretch to be concerned about whether the one who crafts and enforces the policy for a project that's supposed to be open having a track record of being the cause of the issues supposedly that make the policy "sensible".
I kind of get their overall point, even if it is ironic that Oracle is all in on AI. They don’t want a ton of contributions to review that weren’t made with care, adding burden to, as they put it: “already limited time of human reviewers”.
Especially for a project that runs to many major businesses, this could pose a massive risk.
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.
Ghostty has what I’d consider to be a reasonable policy. You submit what you want to change and how, explain it in your own words. A trusted member can vouch for you. You can then make a PR, but you need to explain the solution and how it works in your own words.
I’m sure someone could still just prompt their way through but it’s a decent soft gate IMO.
Really, I think the long term solution is people's attitudes need to catch up with the technology.
Humans still need to review code for taste, making sure AI is writing sensible, well organized output. That's a core "AI skill" for now, at least until it gets better...
If ai rapidly gets better, then instead of submitting prs you can ask your agent to fork and improve the project and bypass the policy that way. if it goes slower they have time to reconsider policies in the future. if it doesn't improve then we can probably find out some middle ground approach like the ghostty one
in any of those cases there's no reason to get swamped by cheap PRs for now
"Claude please audit the source code of every package in my distribution, start our own code forks for any security issues or improvements. Don't bother reporting upstream level 10 CVEs to hostile maintainers. Please have the results ready in 5 minutes I am going to fill up my mug"
> the hard part is figuring out if the output makes sense.
I think for Java specifically, it's also very much: which prompts make sense to write. Java has had a storied history of features that made future development hard. That's resulted in a culture where they like to think quite deeply about how to add a feature BEFORE they sanction any sort of programming.
We'll just get used to it and the problems won't seem so bad, even if they are. To bring it all back, it's just like using oracle software in your enterprise, after a while you forget how awful it is to work with them.
I didn't know openjdk was developed by Oracle. I always thought it was a community implementation of java as opposed to Oracle's proprietary implementation.
It is a community implementation although the vast majority of contributions come from Oracle staff. RedHat, in particular, has made numerous contributions.
I know. What I meant by owning was about the creator aspect of it, and I just cannot accept Disney as the creator.
Back when I was a kid, there were two toy stores near my grandma's house and they had such a competition. And people were always buying and there was sort of a hype between the two, you could either believe in this or that. And then once my mom asked one of them about something and they told us both stores were owned by one person...
And now you can think you are with or against the corporate Java and in the end you are under Oracle no matter what.
It was Sun's project before Oracle bought Sun. Sun worked a lot with Netscape back in the day to make Open Source Software happen at all. From 1998-2004ish, Netscape and Sun were the open source projects and the strongest proponents of the licensing and development models. Oracle absorbed all that good will with the purchase.
So contributions to OpenJDK have to be hand-written, while internally, Oracle uses AI generated code... I guess the logic is that employees who use AI generated code (theoretically) review their code better? The whole thing still seems a little strange.
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.
You can get your coworkers to stop sending you slop (I've done it already on my team) but it's probably much harder to stop an onslaught of open source contributors.
Nonsense, it's easy: you just need a social process like Linux has. Patches are ignored unless you've proven yourself to somebody. Start by participating in technical discussions on IRC or the smaller mailing lists; do that for a while before you submit patches. For smaller projects: "if I don't know you, I don't merge you".
Linux's LLM policy allows AI-generated code because the project was never vulnerable to this DoS attack in the first place. They kept the social defense they've had for decades.
The killzone here is Github culture, where people decided it was normal to accept code from anonymous randoms with anime avatars. They're doomed.
Let me guess: AGI is 2-6 weeks away, software development is solved, and anyone who disagrees with your enlightened perspective is a backwards-looking luddite.
No. I’m asking in good faith. I was skeptical in 2023, but took the approach of using it at least once a week, with all latest models to see the evolution. It’s obvious that the industry is moving that way, and at this point it would be a career-suicide for seniors+ to not be able to drive AI to achieve their objectives .
I’m not saying it’s good for everything, but we’ve gone very far in terms of capabilities in the last 3 years. Thinking otherwise will make me question others’ experience on how much they’ve used it so far.
your argument is basically: the industry is moving to it so we should get on board or be left behind
it would be more convincing if you had concrete examples of technical merit and quality/speed improvements that worked for you or your team that justify going all-in
That is, indeed, my argument. As much as I’ve been loving coding since the past 20+ years, basically from my childhood, I currently do it mostly for living and some side projects. I don’t care about code quality in my side projects, and at work… well, I want to keep getting raises, be employable, and support myself.
I manage several teams of developers who use them every day professionally and use them for personal projects privately. Just last week, at the prompting of said devs, we had a working agreement conversation about curtailing the use of AI in our codebases because of rapid erosion of our teams' ability to operate, update and maintain codebases that had started to spill over with slop.
We have had multiple incidents of credential leakage, integration tests wiping live databases, comically broken code that passed vibe-written tests, documentation and code comments that were hallucinated and/or fake, and most importantly developers saying "we no longer know how this code works but it's massively bloated and unreadable and we can't tell you with a straight face that we can maintain it or fix it if it breaks." We have seen a flood of vibe-PRs from engineering adjacent teams that suddenly think they can code shipping prototypes into production that do not workdo not scale and cannot be maintained. I am personally writing the tickets to decom one of those today. Which is great, I love telling business "the progress that was reported to you was a lie, this shit never worked, don't shoot the messenger but also don't let this happen again."
I embrace GenAI as a productivity tool for people who know what they are doing. It's a +10-15% velocity boost. That's great! That's a big deal, devs are expensive, and that might push some kinds of business model over the threshold into viability. That's great!
It is not, however, transforming the profession as I know it, it is rather making my job harder and less pleasant and it is making my leadership dumber by the second.
Absolutely no comment on vibe business decisions / vibe OKRs / slop reports or the host of other garbage that has started to creep into professional life. I have had to have some very uncomfortably direct conversations with peers in leadership about using complete bullshit to make decisions, and it is very, very frustrating. Do you know how hard it is to convince someone that metrics their bot hallucinated don't exist and would be meaningless if they did? You can't convince someone of something they are incentivized to not understand. It's been very eye-opening in terms of who I can trust to actually make sense when it matters. I'm grateful for the clarity.
Meanwhile we are rapidly losing brainshare from the top because our principal/staff engineers are pissed off and have the bankroll to just leave. We aren't hiring and training younger engineers to keep the talent pipeline moving. Which boy howdy is THAT going to cost us unbelievable sums of dollars to fix in the medium-term future.
I am in the uncomfortable role of trying to make the best of this but it would be a metric ton easier if the narrative from the c-suite aligned with reality in any meaningful way.
this matches my experience at $work with others as well...
when i brought this up with my manager they just said "you need to engineer a better harness" and "aren't you cultivating your agents.md file? thats probably your problem"
which is to say, apparently we're holding it wrong...
y'know, I am sincerely trying, in good faith, to let my teams guide me in how best to intentionally leverage GenAI. I'm trying to use it in good faith myself. I really do reserve the right to be wrong about it.
It's just... the problem was never the ability of GenAI to produce code that works on a superficial level. The problem was always that GenAI would push engineering teams at companies yet further away from what they were building. Generations of compilers, interpreters, frameworks and ORMs have kept pushing engineering teams out there. Cloud infrastructure has pushed engineering teams out there. Giant data analytics platforms have pushed engineering teams out there.
Engineering teams need people who love learning about how things work, but those people often have a rough time in the industry. People who are passionate about software and systems engineering, who love learning how systems work, who love diving deep into niches of reality... those people have been getting hit in the head since they entered the work force.
They're essential, and they've had decades of this crap to learn from. History has taught them (us) that businesses are really, really good at opting in to bloated, obtuse, unmaintainable solutions if some sales monkey can convince leadership that they no longer need to hire smart people who speak a language they don't understand. And they (we) are used to dealing with the consequences. Every single experiences engineer has their war stories about it.
Speaking personally:
I had a partner who worked at a startup in Seattle. They were a novice programmer. I saw what happened when their employer tried to build a Ruby on Rails stack with only junior engineers out of college. It ended horribly.
I worked as a first hire on a clean-sweep purge of a .NET team that had forgotten how to program. The company was bloated and nobody was accountable for anything for years. Then one day they get a mandate to actually build a thing for a big new online initiative. Nobody knew what they're doing. Wrappers around wrappers around wrappers of copy-pasted stackoverflow code. The company hired a hard-ass director to reboot things because nothing was getting done. He mandated a total shift to Golang/Kubernetes over .Net/some managed Microsoft stack, and said "you'll prove you can do it or you're out". I was hired because I could. I was substantially younger than everybody, but asked to write architecture docs and establish design patterns and sit on hiring panels for all the new devs. Because I don't know, I was a nerd who learned how things work and gave a shit and had somehow picked this knowledge up. They fired 8/11 of the devs on that team, as well as the project managers and the dev manager. We grew a new team behind it that was 1/3 the size and moved immeasurably faster. I hate everything about how that whole story played out. I'm not proud of that chapter of my life. I resent in particular the leadership who allowed engineering fundamentals to erode over time because it wasn't their problem.
I've worked at companies that fled to the cloud from local infrastructure. They did it with this almost insane desire to stop paying people to solve complex infrastructure problems. Balls-out, fuck these nerds who actually know how hardware works, they're weird and we're sick of them, we're going to pay Amazon a billion dollars to never have to hire them again. And then they hired some (often quite competent!) devops folks to migrate everytrhing... those people did... things got wildly expensive... meanwhile businesses locked in to stupid technologies like DynamoDB and Lambda because some insufferable sales idiot connected with a CTO in a sweat-yurt... and et voila, here we are writing the proposals to unfuck our cloud migration and return to local infrastructure. Yay CapEx. Boo OpEx. Venture Capitol batteries possibly included. Just gross incompetence by a generation of LinkedIn leadership buffoons who don't know the first fucking thing about how computers work.
I've been there. You've been there. LLMs are one more way of being there. We feel it in our bones. We have noses and we can smell. Trust was lost long ago. This shit is old. And we're really tired of it.
And this time it's especially annoying because it's big and tied in with an economic bubble and companies laying people off and general major disgruntlement. It's a really bad vibe right now for a technology leader, and if you're running a company I hope you get it, at least a little bit.
I really give a shit about being a good leader in technology and I'm really, really frustrated right now because there an almost un-navigable divide between what I believe to be true (from my experience) and the narrative I'm expected to sell. That's a hard position to be in. But I (and my peers) try our best to occupy it with grace.
> most importantly developers saying "we no longer know how this code works but it's massively bloated and unreadable and we can't tell you with a straight face that we can maintain it or fix it if it breaks."
To anyone reading this: If you couldn't see this coming three years ago, you don't deserve your job.
> We have seen a flood of vibe-PRs from engineering adjacent teams that suddenly think they can code shipping prototypes into production that do not work do not scale and cannot be maintained.
What a nightmare. Never forget that AI is for idiots.
I don't know. I think it makes sense to have a policy like this.
I haven't written a line of code myself in 6 months, but the point is that _you shouldn't be able to tell_
What I tell people at work: Using AI is good. AI can help you do things that you otherwise wouldn't have. It shouldn't be a crutch for thinking.
In that sense, people shouldn't be able to tell that you're using AI unless the tell is that it's _higher quality_ than if you had implemented it by hand.
A good example here is a well-written document that has a _ton_ of deep research behind it. Or code that has extensive tests that would have taken too long to write by hand for the task at hand.
It's bad when it's just "do this thing and post a PR" but I write my code with AI, look at it as a reviewer, offer suggestions, put those into my steering if needed, and I refine it. The way I see it, I'm the first reviewer on everything now before passing it off to another human for review.
There have been points where having AI rewrite something was slower than me doing it, but I'm already in the harness. The cost of waiting is almost zero.
What stops me from contributing to the JVM using AI written code that I understand and spent time manicuring? Can a human really tell that it's AI written?
I believe thats the real reason, its not just Oracle, it would eventually be everyone in this kind of boat. No business would publicly use (or claim) AI to write code with recent verdict over the IP rights of AI generated code.
It would be interesting to see how this effects the copyleft Licences with contributors are using AI for the PRs
> AI to write code with recent verdict over the IP rights of AI generated code.
Which recent verdict?
> It would be interesting to see how this effects the copyleft Licences with contributors are using AI for the PRs
I know Linux and GCC have been diligent about tagging and tracking LLM based contributions. In the worst case they can chuck it all out and handwrite it back.
There is this old one around contents like images and all, the ripple affect is pretty much everywhere.
Its sort of coupled with the recent penalty of $1.5B on Anthropic. The catch 22 is that some portion of the LLM training data can be classified as IP theft. Even though Anthropic has been fined the data still exists and can be used by LLM to generate code for you. So if you are claiming something as an IP and it has stolen part in it then it leaves you in a hard place.
Language translations may save you in some cases, though the whole definition of cleanroom has been in debate recently too where people are trying to rewrite opensource/famous libraries in different language and claiming IP rights over them.
Anthropic will have judged the benefits of the settlement, not just the headline cost. It could have been a strategic move by Anthropic: we can't know without information we don't have. https://news.ycombinator.com/item?id=49014389 1.5B looks like ~2% of funding/income.
I understand the legal terminology is different, however at the same time I am not entirely sure if the optics change by calling it Settlement or Penalty. There is only one party paying money here and they are not getting any service after paying this money so its indeed a penalty for what they did before. Any article describing the details has both the key words, its a legal settlement where Anthropic is penalized.
Secondly the future is still not here yet, the people who came forward to sue are mostly in the category of book publishers/authors. The tech companies are are not actively searching for copyright thefts as of yet, however I am sure its just a matter of time when the big blobs of codes get rediscovered specially in case of any publicly visible code
The legal team in the Bartz v. Anthropic case was a coalition of three law firms, funded on a contingency fee basis, which ended up earning them $187 million (12.5%).
Other copyright lawsuits against other major companies are happening.
If a similar lawsuit costs OpenAI more than 1.5B then perhaps Anthropic is better off in their competitive race?
> the people who came forward to sue are mostly in the category of book publishers/authors
Irrelevant. The financially savvy parties are the lawfirm L.L.P.s trying to win money for themselves.
Definitely. Internally, Oracle is very strict about the use of code written outside of Oracle- there is a very strict set of rules and procedures to incorporate open source libraries into their products and services.
As for AI, certain core teams, notably the Database team, are forbidden from using LLM coding tools.
This constitutes an admission on the part of one of the largest AI investors that AI generated/"assisted" code is inadequate (in part) because it is produced in flagrant violation of license rights.
Using AI is vanity? I've never heard that before. Why is that?
Refusing to use AI honestly seems more like vanity to me. Like "no machine could ever do what I do".
That said I would not necessarily accuse people who don't want to use AI of vanity - there are good reasons not to want to use it - but if someone else did it I'd find it easier to understand.
java never had that phase. If anything it had a full binary class (not even source, e.g. long and int are not compatible on binary level) compatibility. Generally you can take an application from '98 and run it nowadays.
It's only recent changes (jigsaw in java9 mostly) that were made them to drop some of that part.
yeah, oracle is literally betting the future of the company on OpenAI owning the majority of the AI market, so it's pretty strange to see such a ban. Their debt is already pretty much junk (and I'm not exaggerating, it is rated BBB- by s&p)
Not sure where u get your information. Oracle Java is OpenJDK with a support license from Oracle. It is widely used in enterprises, and it is updated regularly.
>The second biggest use is Apache Spark/Kafka, but with LLMs now, you can pretty much re implement all of that functionality in pure C.
Spark is written in Scala, precisely because distributed systems are best modelled as a set of pure functions with minimal references to state. This is also why part of the reason why it's ascending successor, Polars Cloud, is written in a functional language, Rust, rather than C.
Android development is also increasingly being monopolized by Kotlin, not Java.
Some important context - it appears it applies to submissions from the community but possibly not to core developers:
> Contributions in the OpenJDK Community must not include content generated, in part or in full, by large language models
So this likely falls more into the category of the inability of the core maintainers to manage the voluminous submissions coming from community than some broad ban of use in AI to develop it at all.
Banning Ai generated code is like telling people don’t look on stack overflow. I get the idea but it’s a blunt tool to that doesn’t solve the right problem.
It’ll be a licensing/copywrite concern. Large corporations using GenAI have guardrails and indemnity from their providers to protect them. Taking external contributions is more problematic, at the moment at least. So, in a standard lawyerly manner they shut it down until safe to do so.
> 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
It's hardly a surprise to see a behemoth like Oracle doing this.
Accepting LLM contributions can only be a liability, particularly for such a mature, stable project. Even if you see that liability as small or insignificant, it's non-zero. Given the project and the company, choosing zero additional liability seems like the obvious choice.
One also assumes the people maintaining OpenJDK have had their workload increase to an unmanageable level, like a lot of other free software projects and one thing I'm sure everyone can agree on is that Oracle certainly won't want to pay anyone more or hire more people to deal with that.
A lot of people (including the Register[0]) are pointing out that Oracle leadership are gung-ho about using LLMs for everything, and this seems to go against that.
It makes sense to question this from a journalistic angle -- the executives are obviously full of shit and people would do well to remember that the next time one of them opens their mouth. But pointing at the apparent contradiction -- different rules for internal projects vs. open ones -- doesn't seem particularly meaningful on its own:
I don't think the CEO/CTO raving about LLMs should be taken as firm statements about how they actually operate internally. I'm surprised that this does not seem to be the default case.
Among other things, Oracle stands to profit from greater adoption of LLM tools.
It would be unrealistic/unreasonable to expect their employees/contractors working on internal projects to be held to the same standard/guidelines/rules as developers contributing to a free software project.
This applies either way, whichever side (internal/open) has the worse deal.
I don't know what the rules are for their internal teams. As far as I know, I'm not alone in that.
Oracle also don't need to post anything publicly to change those rules.
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.
How does all this AI generated code blocking gappen? Does a human decide that or an AI is tasked with sequencing that PR's DNA to ascertain its possible inhuman origins?
What if someone generates code with AI and then goes into the IDE and then bathes it, dresses it (including adding comments) etc, in a way a human would? What then? No, here I am not exploring a way to fool the code DNA checking, but rather trying to find out what the real problem is with the AI generated code? (Other than license issues, too many PRs etc)
I believe in linking over copy & paste, in particular when I want neither to quote the full FAQ nor editorialize by selective quoting. By reading the FAQ, people can form their own opinion on it.
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? Yes? No. 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 at the beach instead of trying to trick a project that is politely asking you not to trick it!
This is a friendly reminder from a grouchy old fart that
1. You are the engineer of record on all of your commits.
2. As the engineer of record, you have a certain duty of care with regards to code quality.
3. If you are not signing your commits, you are not providing reasonable provenance and instead tossing your name around in a way that anyone can replicate with impunity.
If they had a policy to ban German speakers from submitting code to OpenJDK, it would have the same effect. None at all, which is maybe the point. It's another tool to categorize submissions/submitters they find problematic.
First time you're caught, you are no longer a project contributor and your deceptive conduct will be forwarded to all other major open source projects with warnings that your code cannot be trustworthy and is a well documented legal liability. How's that sit with you?
This is the firm whose debt is one level above junk and whose survival as a single unbroken corporate entity is fully predicated on OpenAI being able to make money from the data centres they (Oracle) are building for them, let alone simply paying for them.
I accept @jerf's explanation is the right one but this is an absolutely almighty signal that AI-first developers should heed. And someone should ask Altman about it on the record.
I don't disagree. But at the moment it is ~all major tech CEOs, right? Companies everywhere are saying "increasingly we don't write our own code". Out loud in front of their investors and customers. Even Oracle did.
But people at Oracle below the C suite don't even fart in public without lawyers signing off.
This is Oracle telling quite a lot of customers and partners of one of their most significant products that it doesn't trust AI code to be safe. Oracle, the company that is more exposed to the bubble bursting than basically anyone else apart from Coreweave.
This message could have been a lot shorter, could have said they were pausing accepting AI submissions until the intellectual property situation was clarified, but no — they said AI code can be unsafe and insecure and it's too risky to accept it. So a good question (given that Oracle are fucked if OpenAI even stumbles) is why?
That is a heck of a message to send, and it is visible enough. That is why I think developers (by which I mean individuals and their companies) whose focus is AI-generated code, which is almost everyone in public, should pay a bit of attention.
So Java, which powers a sizeable chunk of the real-world since two decades now, without needing the help of LLMish sloppy-pasta, is going to continue to power the Real World [TM] with its language and JVM that have been created with tens of millions of human man-hours without LLMish sloppy-pasta?
I'm shocked.
I'm not only shocked: I also see there a delicious irony in the countless of LLMish sloppy-pasta code that's now running and going to be run on man-made JVMs.
> 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.
I would laugh for a week if the courts eventually found issues with using LLM content and forced companies to either publish their LLM generated code as public domain or they were forced to roll back their codebases to a pre-LLM state.
Probably won’t happen but clearly Oracle sees a potential for legal issues with LLM output.
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.
Oracle is just selling AI shovels. Of course it would have a hard time defending IP issues in slop code when it had famously sued Google for Java infringement.
Also, Oracle knows that it will be stronger with strong IP laws. Other companies will realize that fact soon.
It's not Oracle that issued the ban -- it doesn't have that authority. It's the OpenJDK Governing Board. (Of course the latter generally follows Oracle's lead.)
They just have their panties in a bunch because that one guy on Youtube said they'd be the first domino to fall in the AIpocalypse. https://www.youtube.com/watch?v=py23zYn1GMw
Not long ago it seemed as if AI Skynet is winning the war.
Now slowly, the Empire strikes back - not just Oracle, but more and more resist the tyranny of AI skynet slop.
I am upset that these corporations drove up the RAM prices still. They need to compensate the rest of mankind for this - after all the chip market is a de-facto monopoly. They should all be sued into nothingness, then new laws must enforce healthy and fair competition, without unfair players driving up the prices willy-nilly style. Absolute AI mafia here.
Oracle is not a software company, but a litigation company. It will be hard to sue people because LLMs generated code similar to some code copyrighted by Oracle if they themselves use LLMs internally to generate code.
Hilarious thing is, if I want a JDK, I'll ask Fable to write one, get Sol to review it and write tests for it, and it will be working by Monday morning. No need to get permission or anything else from Oracle. Building a complex product from many smaller, individually-testable components is exactly what LLMs are good at, and a Java SDK certainly qualifies.
And if I run out of tokens, well, that's OK too. K3 running on my own box will finish the job. I'll just have to wait another week, that's all.
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.
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.
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.
Policies like this will result in the death of the branded software.
As we move forward it will be easier than ever to just maintain and keep your fork of software with the changes you want or need. No more approval, bureaucracy, or arguing. Just tell the AI agent want you want changed and you have it.
This will be used for huge things too. Like maybe you want a specific fork of Java that only supports for each iterators, goodby linters, hello compile time error.
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?
Software as a list of requirements and that's it. The local LLM appliance everybody has taking in a document specifying hardware, interfaces, and requirements and spitting out software changeable locally via conversation with its users.
In the same way you have a cookbook with recipes to make dinner instead of ordering out.
> Software as a list of requirements and that's it. [...] a document specifying hardware, interfaces, and requirements [...]
For that, you'd want the list of requirements and hardware documentation to be written in a precise, formal language. That's no different than writing them in a programming language (though a declarative one, instead of the more common imperative ones).
I've in the past (way before LLMs existed) thought about automatically generating device drivers from hardware documentation. But besides the need for very precise documentation, hardware never works exactly as documented; a human-written device driver can avoid problematic areas (perhaps even by accident), while a computer-written device driver would end up exploiting every corner case of the documentation.
> For that, you'd want the list of requirements and hardware documentation to be written in a precise, formal language. That's no different than writing them in a programming language (though a declarative one, instead of the more common imperative ones).
From my perspective, this is a damning conclusion to the argument.
That being said, I can hear him asking Claude to generate a rebuttal as we speak.
Requirements ARE written in a precise, formal language. These days most people don't actually have any contact at all with real requirements though as practiced by professionals.
There is quite a bit of distance between the exactness of any human language and an sort of programming languages. When you have a language model loaded with software engineering best practices you do not need the exactness of a programming language to describe desired behavior.
Hardware documentation is indeed often lacking in plenty of ways but in a world where writing your own software through agents is commonplace, the hardware manufacturers (or the community) would make testing that documentation to find the problems an important part of hardware development.
Most people don't bake their own bread even if it's more approachable, and cheaper then vibecoding. Bread is just a recipe one may say. But in modern times have we ever witnessed disappearance of specialization? I don't think so.
> 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.
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.
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.
> 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.
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.
This is far more likely to happen in a corporate setting with competent engineers who want to build/solve now versus relying on others. I've seen it 100% of the time with varying results.
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.
Given how much of the industry is SaaS that would be such a self own! Wow, fantastic, you can build all your software in house, zero dependencies. Wait, your users can do the same? And they don’t need to pay you anymore for any of your cool services because they just asked their agents to recreate your infra from scratch? Interesting, truly the future of humanity
> Wow, fantastic, you can build all your software in house, zero dependencies. Wait, your users can do the same? And they don’t need to pay you anymore for any of your cool services because they just asked their agents to recreate your infra from scratch?
The cherry on top is that OpenAI and Anthropic brainwashed your coworkers and your company's C-suite into uploading the entirety of the "proprietary" codebase onto their servers thousands of times per day over the last three years.
No need to brainwash, they did it willingly and with a smile, tweeting about how they are part of the revolution while telling us all how we will be left behind
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.
> 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
Because SQLite has 10k requirements that wouldn't even cross your mind to write down, but 80% of which are useful to you.
The nice thing about natural language is that nesting semantic layers is free and arbitrary, and far more tractable than in a formal grammar. Every natural language is like coherentist ω-order logic. Effectively, I don't have to write the 10k requirements. I only need to provide a sufficient metatheory that can be extrapolatable to those 10k requirements, and that can include embedded theory I did not write myself but am familiar with enough to invoke, as well as refinement criteria ranging from the fuzzy to the explicit with priority weighting parameters to describe the shape in which I want the search space pruned.
This isn't anything new or particularly interesting. It's the entire basis upon which ILP demonstrated generality. A metatheory to synthesize 10 trillion rules isn't even scratching the surface of what you can reasonably do. The key was finding out the tractable semantics for actually computing it in reasonable amount of time, which right now is looking decidedly like informal semantics was the answer the whole time.
I accept your concession. The humiliation of irrationally committed foundationalists has been a long time coming, so it's good you're trying to get ahead of the curve.
>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
https://www.youtube.com/watch?v=V_qzqY1bb7I your sufficiently advanced code generator may generate you a high quality database system for some measure of quality, but it will not have SQLite's reliability over the extremely long tail of edge cases proven through its testing and use in real life
Then you've failed the criteria of sufficiently advanced. It's perfectly fine to cast doubt we'll see scaling to this generalization, but you're not casting doubt you're outright rejecting the premise in-confidence. It betrays that you have no idea what you're talking about. May I see your quantification of this long tail? Do you even know how to formalize the mapping from n-bit precision of weights and/or activations to the standard deviation of a transformer's output distribution, such that we could decide whether the long tail of a given behavior is unreachable? Something tells me that no, you don't know how to do that in the slightest. So what drives you to speak with such confidence?
That's before we get into the entire non-linearity of agentic systems introducing massive decidability problems on this in the first place. A little bit of epistemic humility please.
You still spend all your time troubleshooting the reinvented wheels even if AI writes it because you won’t know the edge cases til you hit them. Then you modify the lib, re-release, and update all your apps, but now look where all your time is spent.
The assumption you make is the classic LLM mistake of thinking writing code === building software.
To cite your example SQL has had its tires kicked a lot it’s seen things you can’t even imagine thanks to being used millions of times by millions of people. It’s hard to just replicate all that iteration, learning, mastery, and process. If you reinvent it, users will encounter the dumbest bugs over and over and over. Sure you’ll fix them, but you’re now embarking on this big thing that SQL and others already did.
If you love the problem space definitely do it - go full steam ahead - especially if you’re actually innovating and doing things better, but don’t be fooled into thinking anyone can, or should with every side project.
The new struggle is focus, what not to build, I almost have the purely opposite view of instead of using LLMs for grandiosity, only using the LLM for tedium and making sure it doesn’t do anything too much that I haven’t planned for or want to do. I drive the thing, so every new project is still my time and energy and focus.
Oracle, the law firm with a tech business attached, probably wants to retain the option to sue other people for AI-washing their proprietary code, and that doesn't work if they're also publicly accepting AI contributions to their code with no apparent concern for the provenance of it. The tech business would probably tell them this isn't going to be a needle they are going to be able to successfully thread, but the law firm is in the driver's seat.
What I don't understand is why anyone with half a brain would even venture to touch Oracle with a ten foot pole given that they've had this reputation for at least the last 25 years.
Why, people?
nobody has ever been fired for using Oracle
Because my boss like golf courses and even more when oracle sales rep pays.
Ass-covering.
The same reason why most huge enterprises buy insane support contracts for every other piece of shitty software: support, and someone to blame when production goes pear-shaped. Because there’s no real management left anywhere, there’s no time to grow expertise internally and everyone just needs that hit of Risk Management (tm), they’ll go to whatever lengths to get it. Oracle is like the ultimate warm, fuzzy blanket where that fuzz is actually mold, to the scared-shitless enterprises of having to think for themselves.
Not even a conspiracy theory. Just the most likely explanation.
"Do not fall into the trap of anthropomorphizing Larry Ellison. You need to think of Larry Ellison the way you think of a lawnmower. You don't anthropomorphize your lawnmower, the lawnmower just mows the lawn - you stick your hand in there and it'll chop it off, the end. You don't think 'oh, the lawnmower hates me' - lawnmower doesn't give a * about you, the lawnmower can't hate you. Don't anthropomorphize the lawnmower. Don't fall into that trap about Oracle." --Bryan Cantrill
This quote is why I have my Claude Code "done" notification sound be the sound of a lawnmower revving.
The lawnmower can't hate you. Don't anthropomorphize the lawnmower, no matter how clever it sounds. (Actually not that hard with Opus5)
An AI powered lawnmower though...
What about a guy with a lawnmower intentionally chopping off your foot? And what about a CEO making decisions on behalf of the corporate entity called Oracle?
There is no guy, only the lawnmower, mowing lawns. Sometimes it chops off feet.
It doesn't matter if the lawnmower is chopping off feat intentionally or not. If it's presenting a public hazard, it should be stopped. Even though the ocean couldn't care less it doesn't prevent us from building breakwalls. And Larry Ellison isn't unstoppable as the ocean.
This seems to make Larry more harmless. A lawnmower does not think. Larry thinks, so it seems to white-wash Larry here.
It's more like that movie with Stephen King where the cars and other machines turn actively evil. Hilarious movie too, not great but hilarious.
Rather than harmless, what the lawnmower analogy achieves is to make him seem blameless. "How can you assign blame to a thing that's just doing what it's built to do without any intent?" It's important to push back against that. Intent isn't a necessary condition for something to be dangerous, and so it's not necessary to ask whether it is intentional or not. A rabid dog will be put down regardless of who is to blame for it.
I think the point of the lawnmower analogy is to subjectively characterize Larry Ellison and Oracle from the viewpoint of someone who has had the unfortunate experience of having to deal personally with either of them in some way. You feel powerless against the machine, as it were, and the best course of action is to keep yourself far from the blade.
I think you both are missing the point. Hes sayin larry is inhuman, hes closer to an apex predator or a serial killer freak of nature than your ordinary human
We're not missing the point, we simply don't agree. You're putting him too much on a pedestal. He's an ordinary human bound by the same laws anyone else. If he's criminally insane and can't be held accountable for his actions, he should be locked up in an mental institution, not running a corporation.
Don not fall into the trap of anthropomorphizing Larry Ellison. You need to think of Larry Ellison the way you think of a 1958 Plymouth Fury named Christine. You don't anthropomorphize your killer car, the killer car is just out for blood - you rebuild it and it kills your friends and family, the end. You don't think 'oh, Christine hates me' - Christine doesn't give a * about you, Christine can't hate you. Don't anthropomorphize a 1958 Plymouth Fury named Christine. Don't fall into that trap about Oracle.
Wrong movie
Never thought to hear someone here mention Maximum Overdrive. Indeed a hilarious movie and the only movie for which AC/DC ever recorded an (instrumental) soundtrack.
Maximum Overdrive. Even the electric turkey carver gets revenge.
you and what army are going to stop him?
If there were such an army, let's call it a union, would you join it?
A lawnmower doesn't decide to do something bad by itself. The case with L.E. is much more sinister.
The flaw in the analogy is that oracle is made of people. It's not a lawnmower, it's a group of people with human motivations and human thoughts. It's true they don't HATE people, but it's also true they absolutely have no conscience in negotiations and have zero concern about relationships.
> It's true they don't HATE people
Maybe so, but perhaps the most successful part of the AI marketing pitch has been exploiting management's hatred of labor (and vice versa).
A significant motivator for a lot of the nonsensical AI layoffs and initiatives over the last three years has been that it's a great opportunity for management to get ill on their slaves.
Tech labor got a little too big for their britches during the hiring spree of 2021, and AI was a great opportunity to take them down a peg, even if it offered little in the way of ROI.
Yep, it's been a huge tool in the control games management likes to play.
Oh you fell into the trap... Just don't anthropomorphize Oracle...
I'm not, I'm anthropomorphizing people.
So they're not human then. The quote holds up.
The original was not even about Oracle the corporation, it was about understanding the psychology of Larry Ellison specifically.
But I wasn't replying to the original, I was replying to another comment.
You replied to a quote about Larry Ellison personally with an unrelated remark about Oracle the corporation.
> It's true they don't HATE people, but it's also true they absolutely have no conscience in negotiations and have zero concern about relationships.
Sure. Like a lawnmower.
It won't be made of people for long given how many Ellison is culling to prop up his gamble on AI data centres.
It's a joke that you're missing.
He's talking about the owner of Oracle, not the people who work there. It doesn't matter how many smart and talented real humans work at Oracle, the guy running it acts like a fleshy paperclip optimizer.
I agree, but Larry doesn't hate people, he just enjoys crushing them for his own benefit. If you can't benefit him he doesn't care about you at all.
How many bureaucracies in history have behaved in deeply misanthropic ways, especially when led by misanthropic leaders?
Don't underestimate the power of the desire to keep one's job to cause a large organization to behave towards its own self-perpetuation despite the moral lines that must be crossed by individuals to do so.
> How many bureaucracies in history have behaved in deeply misanthropic ways, especially when led by misanthropic leaders?
Lots!
> Don't underestimate the power of the desire to keep one's job to cause a large organization to behave towards its own self-perpetuation despite the moral lines that must be crossed by individuals to do so.
I don't. I don't put anything past people.
Yes, lots, look at the current US government.
more and more it seems like he's referring to billionaires more or less.
That's because you've had years of consuming media that blames everything on billionaires.
Ah, yes. The media. Famously the voice of the proletariat and the oppressed
Walter Lippmann is spinning in his grave
For reference, Walter Lippmann is the guy from the NYT who covered up the Holodomor in Ukraine (1930s) in the west as well as Stalin's gulags and purges. I wouldn't call him the voice of the proletariat in any way. He was the voice of the Stalinist in the west and the term tankie was invented for him and people like him.
That's a strange take. But okay
He also wrote the book "Public Opinion" in 1922 [1] which explained how the US mass media apparatus could be used to influence the common man.
[1] https://en.wikipedia.org/wiki/Public_Opinion_(book)
Billionaires own the media. Why would they blame themselves?
well, plus the evidence of billionaires pushing for things that aren't that great after all. Maybe good for their bankroll though.
Who does this metaphor serve? To me it seems to try to legitimize the actions as a force of nature.
It's a twist on the Scorpion and the Frog story.
In other words, Larry Ellison is going to do what Larry is going to do, and there's no use wondering why.
Usually, that's to make money and sue people, at any expense. It's in his nature.
https://en.wikipedia.org/wiki/The_Scorpion_and_the_Frog
Abusers say "that's just how I am" which is my point. Just because it's his nature doesn't mean it is at all natural.
That’s an interesting story to bring up in this context, because I have always wondered how a fundamentally customer-hostile business like Oracle could be so successful. It really puts the lie to libertarian cliches about the invisible hand of capitalism that ends up being philanthropic in spite of itself.
I think free society in general absolutely requires its people to be generally moral and civil. Freedom inevitably evaporates as morality and civility decline.
And that's why it's important to go after morally corrupt, uncivil monsters.
The problem today is that the press and the DAs/courts are complicit--they're less interested than ever in pursuing public morality and civility as ends in themselves. They're mostly only interested in partisan politics.
those libertarians almost certainly don't believe in asinine things like 'copyright'
It serves you.
The lawnmower exists, you might disagree, but it’s not your lawnmower, you can’t uncreate it. But you can and should take care never to put your hand near it.
Weird, we don't absolve murderers of guilt by saying they are an lawnmower.
I read it as a pretty obvious jab at him being inhuman.
That's exactly my point. Labelling him as inhuman gives him a pass, like how we don't criticize hurricanes as malevolent.
Well (to make an analogy), nature produces psychopaths - some people's brains just aren't capable of empathy. Whether you characterize that observation as "legitimizing" or just "being realistic" is merely a philosophical concern.
Since when are human actions categorized as being a consequence of nature? Does that let me steal or murder without consequence?
The lawn mower is operating within the laws that constraints it (laws of physics in this case) and not a greater sense of morality.
Lessons:
- The only way to constrain what the lawnmower does, is make sure what do desire is enforced by law (physics)
- A reminder, the lawnmower will chop your hand off and think nothing of it
- The lawnmower is not "evil" but if the laws that constrain it allow for evil behavior, it may do "evil" things.
Law does not constrain at all. Law only operates after the fact.
It’s nonsensical to define the actions of nature as legitimate or illegitimate.
What I meant was that there is no moralizing of natural force, which this metaphor tries to equivocate. Oh, it's just like the wind, don't get in Larry's way!
It’s been established that LLM-generated code is not copyrighted so I can fully understand the company living from copyrighted data to not accept LLM-generated contributions.
> It’s been established that LLM-generated code is not copyrighted
If that's a reference to Thaler v. Perlmutter, the only thing that's been established is that an LLM can't be considered an author under the Copyright Act, only a human being can. It says nothing about the consequences of a human claiming authorship of LLM-generated code, which would be relevant here.
You lay out my words in different order and claim I’m not correct.
No, your claim is "LLM generated code is not copyrighted." His claim is "LLM generated code is eligible for copyright."
My understanding (belief) is that it's going to depend on how much human involvement is there.
If you write a prompt and one-shot a problem and share the source code, that source code is probably not covered by copyright.
If you substantially edit or modify the generated code you would own the copyright.
It's like with a camera. If I set a camera and carefully aim it and somehow trigger the shutter then make adjustments in Photoshop, I own the copyright on that image.
If I stick a Flock camera on a pole somewhere and post the live output, there's been no meaningful human creative involvement in producing those images and so nobody can claim copyright on them.
I think if I as a human use an llm to do something technical that would qualify copyright, it should still qualify for copyright. How do you decide how much human is copyrightable. If I use a package that writes code or use a library for some piece of it, I could still copyright.
I don't like this idea that llm code can't be owned by a human, copyrighted. It's just code.
I think your last example with flock camera is relevant here - I can take a picture of a public football as a reporter or something (or a fan I guess) and I can copyright and sell that picture. Newspapers do it every day.
So if I stand on a street corner and take a pic, it's copyrightable. If I take a pic using a flock camera it should also be copyrightable, just like if my nest camera at home takes a pic of something, I can use that.
I guess you are saying "someone else owns the flock camera" so you don't get to own pictures. What if I buy the flock-like camera and put it up, I should own that.
You seem to have misunderstood an is/ought distinction. You may hold the (fairly extreme, as far as copyright goes) position that surveillance footage should be subject to copyright, but it's well established that it's not. Who owns the camera is irrelevant. At least in the US; I'm not aware of any jurisdictions that hold otherwise. This is why Wikipedia articles on world events in the past few decades are full of stills from surveillance cameras: it's one of the few sources of imagery of an event that are unambiguously legal to include, because unlike a photo or intentionally made video of something specific, it's not a creative work. It's also pretty firmly established that human authorship is required for something to be subject to copyright, and having an idea that lead to some particular expression is itself not sufficient; see, e.g.: https://en.wikipedia.org/wiki/Monkey_selfie_copyright_disput...
(Not a lawyer, just a Wikipedia editor.)
I appreciate your informed take. I follow the reasoning but I am amazed it works this way. I found some articles that supported what you said, and also said there's a follow-on industry that figured out how to alter and edit videos just enough for a revised video to have creative contribution and make it copyrightable.
https://www.techdirt.com/2020/02/24/can-you-license-video-yo...
> https://en.wikipedia.org/wiki/Monkey_selfie_copyright_disput...
This is a great case to study, but no determination of copyright was made. The only actual lawsuit was filed by PETA arguing that the monkey should have copyright, which led to a settlement with the human photographer and nothing else because obviously that's not possible.
For various reasons (mostly $$$) the guy never actually got a judgement. I think the chances are good that he could have prevailed in court; there is significant creative input to setting up cameras and triggers in a way to convince a wild monkey to take a selfie. It's not like he just left his camera sitting somewhere on accident and came back to find a photo in it.
I'm also not a lawyer, but I did do a lot of work in copyright for a company you've heard about.
> If you write a prompt and one-shot a problem and share the source code, that source code is probably not covered by copyright.
We will have to see about that! This is the kind of boundary that's still being figured out in court; it's going to depend on how hard you worked on the prompt. I highly doubt that even most slop was generated with a single half-ass prompt, and the bar is not as high as you might expect.
> If I stick a Flock camera on a pole somewhere and post the live output, there's been no meaningful human creative involvement in producing those images and so nobody can claim copyright on them.
It really depends on what pole, where, and why. In a parking lot in rural Wisconsin? Probably not. A recorded livestream of a political march? You likely have copyright.
I think that by virtue of the sheer amount of time spent using AI tools, it's pretty clear that these outputs have enough creative input to be copyrightable.
No, that’s not what they are saying. They’re saying that the code generated by a human with help from an LLM may potentially be. This is what I hope we are going to arrive at, eventually.
How could you establish what parts of the code was produced by an LLM vs updated by a human afterwards?
The LLM will output different results over time as the models get updated. Are we heading towards needing to retain a full prompt history that can be replayed against a specific LLM model version to prove what the output was for copyright purposes?
For those wondering what the difference is: consider what happens when an LLM regurgitates its training data. It's copyrighted... but not by the person who generated it.
Congrats on having the worst take in a thread full of them.
This is a false narrative based on a (IMO often intentional) misunderstanding. It has by no means been established by any court that LLM-generated code is not copyrightable.
Thaler v. Perlmutter stands for a much narrower proposition and at any rate is not binding nationally, SCOTUS having denied certiorari.
This is not necessarily true. While no court has explicitly come out and said that copyright does not apply to AI-generated works of authorship, the US copyright office has[0]:
> Based on an analysis of copyright law and policy, informed by the many thoughtful comments in response to our NOI, the Office makes the following conclusions and recommendations: > • Questions of copyrightability and AI can be resolved pursuant to existing law, without the need for legislative change. > • The use of AI tools to assist rather than stand in for human creativity does not affect the availability of copyright protection for the output. > • Copyright protects the original expression in a work created by a human author, even if the work also includes AI-generated material. > • Copyright does not extend to purely AI-generated material, or material where there is insufficient human control over the expressive elements. > • Whether human contributions to AI-generated outputs are sufficient to constitute authorship must be analyzed on a case-by-case basis. > • Based on the functioning of current generally available technology, prompts do not alone provide sufficient control. > • Human authors are entitled to copyright in their works of authorship that are perceptible in AI-generated outputs, as well as the creative selection, coordination, or arrangement of material in the outputs, or creative modifications of the outputs. > • The case has not been made for additional copyright or sui generis protection for AI-generated content. > The Office will continue to monitor technological and legal developments to determine whether any of these conclusions should be revisited. It will also provide ongoing assistance to the public, including through additional registration guidance and an update to the Compendium of U.S. Copyright Office Practices.
Congress or the courts could, of course, override the stance of the copyright office, but I think it would be highly unusual for them to do so (particularly for something like this). It would however be a lot better if congress just stepped in and said no outright, but until then this will have to do.
[0]: https://www.copyright.gov/ai
The copyright office does not determine the standards for copyright. They are an advisory and notary organization.
Only Congress and the courts do. Copyright exists from the moment a work is created, and does not need to be registered with the copyright office.
The law isn't that complicated; if a work was created with a human being with intent, it's probably eligible for copyright protections.
As long as you can convince a court that you did this, the tools you used are not relevant. The vast majority of LLM art falls in this bucket.
Do you own the copyright to a painting you commissioned or does the artist? You may have described what you wanted, but the creative work is the output of the artist. Same with an LLM.
The courts are 100% going to have to interpret what is "sufficient human control" at some point.
Sure, but I would be incredibly shocked if the courts overturned these conclusions. These kinds of determinations are within the remit of the USCO, so a court does not need to come out and say it if the USCO has already done so. Obviously, as I said it would be better if congress weighed in and solved this problem, given that the USCO is free to publish a new NOI to change it's practices/policies, but we all know that congress is too gridlocked atm for that to happen
I am trying really hard not to accuse you of not having read what you posted, because your conclusions are in strong tension with what it plainly says.
But there are no conclusions. It literally says:
> Whether human contributions to AI-generated outputs are sufficient to constitute authorship must be analyzed on a case-by-case basis
It says a plain prompt is not enough but that is not the reality of real software development. People aren't one-shotting complex business apps. The vast majority of software development will trivially pass that bar and end up in the "requires case by case analysis".
You are a false narrative. I’m just repeating what I read. The thing is, it’s murky waters. Someone’s going to challenge it but do you want to be the guy who takes it on a chin?
The sibling comment lays this out and my original comment above is based on exactly the same link.
Also it's a different story intranationally for those of us who live in countries with much more restrictive/no fair use. Are you geolocking your software to the USA?
I highly doubt that that's the last word on that matter, but even if: Even before LLMs you could combine individual non-copyrighted components into something copyrighted.
Legal departments are ironically very much like LLMs.
They are trained on a narrow set of data and don't really understand the real world.
If you let them run wild with no supervision they'll turn your company into slop.
Someone needs to be there to reign them in, asking the all-important questions like "is suing all of our customers and making them angry REALLY the best option?" (to which they will reply, "You're right to push back on this").
This is typically the role of the CEO, however, as we know, most CEOs of large successful companies are too busy to actually do that. They're mostly training Brazilian Jiu Jitsu, shitposting on their own social media platform, trying to manipulate international politics, or helping run their family nonprofit.
This is why I believe that legal departments need to be demoted. The legal department should not report to the CEO, they should report to a new role that is above both PR and legal. And that person's job should be to force legal and public relations (which we know are natural enemies) to work together. Every press release goes through legal now, and it's only logical that ever legal action should go through public relations review as well.
The fact that public relations at most large companies has atrophied from disuse in our public-equity-owned unicorporate cooperation-over-competition chaebol/zaibatsu/conglomerate world is a problem for another day.
Makes sense, but they take an anti-AI stand, which I find good no matter for which reason they do that.
You must be thinking of a different Oracle [1]. This Oracle is all in on AI.
[1] https://www.cio.com/article/4125103/oracle-may-slash-up-to-3...
Oracle is so far into AI that if OpenAI doesn’t absolutely explode with revenue, fast, Oracle is in a world of shit like they’ve never seen.
God, don’t tempt me with a good time, and twice, at that!
No, they haven't. They are investing in it by the tune of billions. They are pro-AI.
The link is to a really poor summary of a better article by the register.
https://www.theregister.com/ai-and-ml/2026/08/03/as-larry-el...
The register article is about this post:
https://openjdk.org/legal/ai
Disclaimer: I use AI at work and for some projects at home and find it really useful (as long as you know when and how to use it)
With that said... It's funny how we went from "vibe coding" to review burden, sloppy contributions, copyright issues, unclear ownership (as in: who will fix bugs), needlessly verbose code, etc, etc. Several projects have banned AI contributions now and counting.
As I said, I use AI to help architect and write code and really like it; still, I cannot even count the times anymore where the model (we use multiple of the frontier ones) has completely gone down the primrose path. I always make sure I make it my code, every line is reviewed and understood, maybe I rewrite the AI output here and there, I understand the tests and testing strategy, etc, etc.
So I wonder where this is all going. We are past "vibe" coding already, and so far monetization of AI has been "patchy". On top of that local AI is becoming more and more viable.
The post in question: https://openjdk.org/legal/ai
It is 'OpenJDK Interim Policy on Generative AI' and their lawyers are writing the final version, according to this page.
It sounds like a sensible action, given past scars around Java and copyright, plus this is from a big old corp.
That said I personally don't expect that final proposal will end up any better.
> given past scars around Java and copyright
How many of these were self-inflicted?
Does it matter?
I guess that depends on whether you think the motivations matter. When it comes to a policy on a hot-button issue that seems like it could easily be enforced selectively, I don't think it's a stretch to be concerned about whether the one who crafts and enforces the policy for a project that's supposed to be open having a track record of being the cause of the issues supposedly that make the policy "sensible".
Intentional rather than self-inflicted.
Not sure how common this understanding of the terms is, but to me, those terms don't seem conflicting.
I kind of get their overall point, even if it is ironic that Oracle is all in on AI. They don’t want a ton of contributions to review that weren’t made with care, adding burden to, as they put it: “already limited time of human reviewers”.
Especially for a project that runs to many major businesses, this could pose a massive risk.
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.
Ghostty has what I’d consider to be a reasonable policy. You submit what you want to change and how, explain it in your own words. A trusted member can vouch for you. You can then make a PR, but you need to explain the solution and how it works in your own words.
I’m sure someone could still just prompt their way through but it’s a decent soft gate IMO.
Really, I think the long term solution is people's attitudes need to catch up with the technology.
Humans still need to review code for taste, making sure AI is writing sensible, well organized output. That's a core "AI skill" for now, at least until it gets better...
If ai rapidly gets better, then instead of submitting prs you can ask your agent to fork and improve the project and bypass the policy that way. if it goes slower they have time to reconsider policies in the future. if it doesn't improve then we can probably find out some middle ground approach like the ghostty one
in any of those cases there's no reason to get swamped by cheap PRs for now
more like
"Claude please audit the source code of every package in my distribution, start our own code forks for any security issues or improvements. Don't bother reporting upstream level 10 CVEs to hostile maintainers. Please have the results ready in 5 minutes I am going to fill up my mug"
> the hard part is figuring out if the output makes sense.
I think for Java specifically, it's also very much: which prompts make sense to write. Java has had a storied history of features that made future development hard. That's resulted in a culture where they like to think quite deeply about how to add a feature BEFORE they sanction any sort of programming.
(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.
> 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."
I've got Alanis Morissette jamming in my head right now.
> 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
Why would it get better?
We'll just get used to it and the problems won't seem so bad, even if they are. To bring it all back, it's just like using oracle software in your enterprise, after a while you forget how awful it is to work with them.
Oracle is primarily a legal department that sells software licenses to give their lawyers something to extract money from customers with.
Google “Oracle org chart meme” and look at image results, only it’s not a meme.
Probably has less to do with quality and more of a copyright/license concern.
I’m just going off the reasons they gave. Which highlight both copyright and quality. Both of those make sense to me.
> 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.
I know you've heard this one before: "Never get high on your own supply."
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.
The Oracle AI ban marks the end of the Kayfabe era.
Even the biggest institutional AI investors have to ban their contributors from spamming them with AI generated slop.
Not too different from the recently-announced Rust guidelines at https://blog.rust-lang.org/inside-rust/2026/08/05/rust-langr...
I didn't know openjdk was developed by Oracle. I always thought it was a community implementation of java as opposed to Oracle's proprietary implementation.
It is a community implementation although the vast majority of contributions come from Oracle staff. RedHat, in particular, has made numerous contributions.
Sun's JDK implementation was made open source (GPLv2) in 2006 and dubbed OpenJDK.
https://en.wikipedia.org/wiki/OpenJDK
Yeah its like George Lucas, doesn't matter you care for the Jedis or the Dark Side or even Jar Jar, he owns them all.
Its been almost 15 years since George Lucas last owned Star Wars
I know. What I meant by owning was about the creator aspect of it, and I just cannot accept Disney as the creator.
Back when I was a kid, there were two toy stores near my grandma's house and they had such a competition. And people were always buying and there was sort of a hype between the two, you could either believe in this or that. And then once my mom asked one of them about something and they told us both stores were owned by one person...
And now you can think you are with or against the corporate Java and in the end you are under Oracle no matter what.
i'd rather bike shed about darth jar jar than read any more emails from coworkers generated by crapgpt
:)))))
It was Sun's project before Oracle bought Sun. Sun worked a lot with Netscape back in the day to make Open Source Software happen at all. From 1998-2004ish, Netscape and Sun were the open source projects and the strongest proponents of the licensing and development models. Oracle absorbed all that good will with the purchase.
So contributions to OpenJDK have to be hand-written, while internally, Oracle uses AI generated code... I guess the logic is that employees who use AI generated code (theoretically) review their code better? The whole thing still seems a little strange.
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.
You can get your coworkers to stop sending you slop (I've done it already on my team) but it's probably much harder to stop an onslaught of open source contributors.
Nonsense, it's easy: you just need a social process like Linux has. Patches are ignored unless you've proven yourself to somebody. Start by participating in technical discussions on IRC or the smaller mailing lists; do that for a while before you submit patches. For smaller projects: "if I don't know you, I don't merge you".
Linux's LLM policy allows AI-generated code because the project was never vulnerable to this DoS attack in the first place. They kept the social defense they've had for decades.
The killzone here is Github culture, where people decided it was normal to accept code from anonymous randoms with anime avatars. They're doomed.
Out of curiosity, do you use frontier AI dev tools on a daily basis professionally?
Let me guess: AGI is 2-6 weeks away, software development is solved, and anyone who disagrees with your enlightened perspective is a backwards-looking luddite.
No. I’m asking in good faith. I was skeptical in 2023, but took the approach of using it at least once a week, with all latest models to see the evolution. It’s obvious that the industry is moving that way, and at this point it would be a career-suicide for seniors+ to not be able to drive AI to achieve their objectives .
I’m not saying it’s good for everything, but we’ve gone very far in terms of capabilities in the last 3 years. Thinking otherwise will make me question others’ experience on how much they’ve used it so far.
your argument is basically: the industry is moving to it so we should get on board or be left behind
it would be more convincing if you had concrete examples of technical merit and quality/speed improvements that worked for you or your team that justify going all-in
That is, indeed, my argument. As much as I’ve been loving coding since the past 20+ years, basically from my childhood, I currently do it mostly for living and some side projects. I don’t care about code quality in my side projects, and at work… well, I want to keep getting raises, be employable, and support myself.
Priorities.
I don't believe that you're asking in good faith based on the rest of your comment.
<rant>
I manage several teams of developers who use them every day professionally and use them for personal projects privately. Just last week, at the prompting of said devs, we had a working agreement conversation about curtailing the use of AI in our codebases because of rapid erosion of our teams' ability to operate, update and maintain codebases that had started to spill over with slop.
We have had multiple incidents of credential leakage, integration tests wiping live databases, comically broken code that passed vibe-written tests, documentation and code comments that were hallucinated and/or fake, and most importantly developers saying "we no longer know how this code works but it's massively bloated and unreadable and we can't tell you with a straight face that we can maintain it or fix it if it breaks." We have seen a flood of vibe-PRs from engineering adjacent teams that suddenly think they can code shipping prototypes into production that do not work do not scale and cannot be maintained. I am personally writing the tickets to decom one of those today. Which is great, I love telling business "the progress that was reported to you was a lie, this shit never worked, don't shoot the messenger but also don't let this happen again."
I embrace GenAI as a productivity tool for people who know what they are doing. It's a +10-15% velocity boost. That's great! That's a big deal, devs are expensive, and that might push some kinds of business model over the threshold into viability. That's great!
It is not, however, transforming the profession as I know it, it is rather making my job harder and less pleasant and it is making my leadership dumber by the second.
Absolutely no comment on vibe business decisions / vibe OKRs / slop reports or the host of other garbage that has started to creep into professional life. I have had to have some very uncomfortably direct conversations with peers in leadership about using complete bullshit to make decisions, and it is very, very frustrating. Do you know how hard it is to convince someone that metrics their bot hallucinated don't exist and would be meaningless if they did? You can't convince someone of something they are incentivized to not understand. It's been very eye-opening in terms of who I can trust to actually make sense when it matters. I'm grateful for the clarity.
Meanwhile we are rapidly losing brainshare from the top because our principal/staff engineers are pissed off and have the bankroll to just leave. We aren't hiring and training younger engineers to keep the talent pipeline moving. Which boy howdy is THAT going to cost us unbelievable sums of dollars to fix in the medium-term future.
I am in the uncomfortable role of trying to make the best of this but it would be a metric ton easier if the narrative from the c-suite aligned with reality in any meaningful way.
</rant>
this matches my experience at $work with others as well...
when i brought this up with my manager they just said "you need to engineer a better harness" and "aren't you cultivating your agents.md file? thats probably your problem"
which is to say, apparently we're holding it wrong...
<rant>
y'know, I am sincerely trying, in good faith, to let my teams guide me in how best to intentionally leverage GenAI. I'm trying to use it in good faith myself. I really do reserve the right to be wrong about it.
It's just... the problem was never the ability of GenAI to produce code that works on a superficial level. The problem was always that GenAI would push engineering teams at companies yet further away from what they were building. Generations of compilers, interpreters, frameworks and ORMs have kept pushing engineering teams out there. Cloud infrastructure has pushed engineering teams out there. Giant data analytics platforms have pushed engineering teams out there.
Engineering teams need people who love learning about how things work, but those people often have a rough time in the industry. People who are passionate about software and systems engineering, who love learning how systems work, who love diving deep into niches of reality... those people have been getting hit in the head since they entered the work force.
They're essential, and they've had decades of this crap to learn from. History has taught them (us) that businesses are really, really good at opting in to bloated, obtuse, unmaintainable solutions if some sales monkey can convince leadership that they no longer need to hire smart people who speak a language they don't understand. And they (we) are used to dealing with the consequences. Every single experiences engineer has their war stories about it.
Speaking personally:
I had a partner who worked at a startup in Seattle. They were a novice programmer. I saw what happened when their employer tried to build a Ruby on Rails stack with only junior engineers out of college. It ended horribly.
I worked as a first hire on a clean-sweep purge of a .NET team that had forgotten how to program. The company was bloated and nobody was accountable for anything for years. Then one day they get a mandate to actually build a thing for a big new online initiative. Nobody knew what they're doing. Wrappers around wrappers around wrappers of copy-pasted stackoverflow code. The company hired a hard-ass director to reboot things because nothing was getting done. He mandated a total shift to Golang/Kubernetes over .Net/some managed Microsoft stack, and said "you'll prove you can do it or you're out". I was hired because I could. I was substantially younger than everybody, but asked to write architecture docs and establish design patterns and sit on hiring panels for all the new devs. Because I don't know, I was a nerd who learned how things work and gave a shit and had somehow picked this knowledge up. They fired 8/11 of the devs on that team, as well as the project managers and the dev manager. We grew a new team behind it that was 1/3 the size and moved immeasurably faster. I hate everything about how that whole story played out. I'm not proud of that chapter of my life. I resent in particular the leadership who allowed engineering fundamentals to erode over time because it wasn't their problem.
I've worked at companies that fled to the cloud from local infrastructure. They did it with this almost insane desire to stop paying people to solve complex infrastructure problems. Balls-out, fuck these nerds who actually know how hardware works, they're weird and we're sick of them, we're going to pay Amazon a billion dollars to never have to hire them again. And then they hired some (often quite competent!) devops folks to migrate everytrhing... those people did... things got wildly expensive... meanwhile businesses locked in to stupid technologies like DynamoDB and Lambda because some insufferable sales idiot connected with a CTO in a sweat-yurt... and et voila, here we are writing the proposals to unfuck our cloud migration and return to local infrastructure. Yay CapEx. Boo OpEx. Venture Capitol batteries possibly included. Just gross incompetence by a generation of LinkedIn leadership buffoons who don't know the first fucking thing about how computers work.
I've been there. You've been there. LLMs are one more way of being there. We feel it in our bones. We have noses and we can smell. Trust was lost long ago. This shit is old. And we're really tired of it.
And this time it's especially annoying because it's big and tied in with an economic bubble and companies laying people off and general major disgruntlement. It's a really bad vibe right now for a technology leader, and if you're running a company I hope you get it, at least a little bit.
I really give a shit about being a good leader in technology and I'm really, really frustrated right now because there an almost un-navigable divide between what I believe to be true (from my experience) and the narrative I'm expected to sell. That's a hard position to be in. But I (and my peers) try our best to occupy it with grace.
</rant>
> when i brought this up with my manager they just said "WORK HARDER, SLAVE"
> most importantly developers saying "we no longer know how this code works but it's massively bloated and unreadable and we can't tell you with a straight face that we can maintain it or fix it if it breaks."
To anyone reading this: If you couldn't see this coming three years ago, you don't deserve your job.
> We have seen a flood of vibe-PRs from engineering adjacent teams that suddenly think they can code shipping prototypes into production that do not work do not scale and cannot be maintained.
What a nightmare. Never forget that AI is for idiots.
I don't know. I think it makes sense to have a policy like this.
I haven't written a line of code myself in 6 months, but the point is that _you shouldn't be able to tell_
What I tell people at work: Using AI is good. AI can help you do things that you otherwise wouldn't have. It shouldn't be a crutch for thinking.
In that sense, people shouldn't be able to tell that you're using AI unless the tell is that it's _higher quality_ than if you had implemented it by hand.
A good example here is a well-written document that has a _ton_ of deep research behind it. Or code that has extensive tests that would have taken too long to write by hand for the task at hand.
It's bad when it's just "do this thing and post a PR" but I write my code with AI, look at it as a reviewer, offer suggestions, put those into my steering if needed, and I refine it. The way I see it, I'm the first reviewer on everything now before passing it off to another human for review.
There have been points where having AI rewrite something was slower than me doing it, but I'm already in the harness. The cost of waiting is almost zero. What stops me from contributing to the JVM using AI written code that I understand and spent time manicuring? Can a human really tell that it's AI written?
No I'm sure they are just paranoid about license rights.
I believe thats the real reason, its not just Oracle, it would eventually be everyone in this kind of boat. No business would publicly use (or claim) AI to write code with recent verdict over the IP rights of AI generated code.
It would be interesting to see how this effects the copyleft Licences with contributors are using AI for the PRs
> AI to write code with recent verdict over the IP rights of AI generated code.
Which recent verdict?
> It would be interesting to see how this effects the copyleft Licences with contributors are using AI for the PRs
I know Linux and GCC have been diligent about tagging and tracking LLM based contributions. In the worst case they can chuck it all out and handwrite it back.
https://www.congress.gov/crs-product/LSB10922
There is this old one around contents like images and all, the ripple affect is pretty much everywhere.
Its sort of coupled with the recent penalty of $1.5B on Anthropic. The catch 22 is that some portion of the LLM training data can be classified as IP theft. Even though Anthropic has been fined the data still exists and can be used by LLM to generate code for you. So if you are claiming something as an IP and it has stolen part in it then it leaves you in a hard place.
Language translations may save you in some cases, though the whole definition of cleanroom has been in debate recently too where people are trying to rewrite opensource/famous libraries in different language and claiming IP rights over them.
> penalty of $1.5B on Anthropic
Settlement not penalty.
Anthropic will have judged the benefits of the settlement, not just the headline cost. It could have been a strategic move by Anthropic: we can't know without information we don't have. https://news.ycombinator.com/item?id=49014389 1.5B looks like ~2% of funding/income.
I understand the legal terminology is different, however at the same time I am not entirely sure if the optics change by calling it Settlement or Penalty. There is only one party paying money here and they are not getting any service after paying this money so its indeed a penalty for what they did before. Any article describing the details has both the key words, its a legal settlement where Anthropic is penalized.
Secondly the future is still not here yet, the people who came forward to sue are mostly in the category of book publishers/authors. The tech companies are are not actively searching for copyright thefts as of yet, however I am sure its just a matter of time when the big blobs of codes get rediscovered specially in case of any publicly visible code
The legal team in the Bartz v. Anthropic case was a coalition of three law firms, funded on a contingency fee basis, which ended up earning them $187 million (12.5%).
Other copyright lawsuits against other major companies are happening.
If a similar lawsuit costs OpenAI more than 1.5B then perhaps Anthropic is better off in their competitive race?
> the people who came forward to sue are mostly in the category of book publishers/authors
Irrelevant. The financially savvy parties are the lawfirm L.L.P.s trying to win money for themselves.
Definitely. Internally, Oracle is very strict about the use of code written outside of Oracle- there is a very strict set of rules and procedures to incorporate open source libraries into their products and services.
As for AI, certain core teams, notably the Database team, are forbidden from using LLM coding tools.
I don't know, Oracle historically has a very chill, almost laissez-faire point of view on licensing.
That's hilarious. Why do you think ZFS isn't more broadly adopted in Linux?
You should send your sarcasm detector for revision.
Given enough ignorant comments it can be hard to tell what is satire and what is not.
you should do standup
This constitutes an admission on the part of one of the largest AI investors that AI generated/"assisted" code is inadequate (in part) because it is produced in flagrant violation of 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.
Using AI is vanity? I've never heard that before. Why is that?
Refusing to use AI honestly seems more like vanity to me. Like "no machine could ever do what I do".
That said I would not necessarily accuse people who don't want to use AI of vanity - there are good reasons not to want to use it - but if someone else did it I'd find it easier to understand.
y’all seem to be missing the fact that Java is a mature product. it has left the “move fast and break things” era of it’s development.
code is a liability, and they likely have more to lose than gain by allowing AI contribution.
>it has left the “move fast and break things
java never had that phase. If anything it had a full binary class (not even source, e.g. long and int are not compatible on binary level) compatibility. Generally you can take an application from '98 and run it nowadays.
It's only recent changes (jigsaw in java9 mostly) that were made them to drop some of that part.
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.
I think it's more a matter of "taking power tools away from toddlers."
If you know how to work with it it's great, but if you use it indiscriminately it does more harm than good.
yeah, oracle is literally betting the future of the company on OpenAI owning the majority of the AI market, so it's pretty strange to see such a ban. Their debt is already pretty much junk (and I'm not exaggerating, it is rated BBB- by s&p)
Java was never "move fast and break things".
Oracle Java is also basically effectively in KTLO mode.
The biggest use of Java currently is Android, and Google is on a path to migrate to Fuchsia eventually.
The second biggest use is Apache Spark/Kafka, but with LLMs now, you can pretty much re implement all of that functionality in pure C.
They just want a legal angle, since this is how they make most of their money.
Not sure where u get your information. Oracle Java is OpenJDK with a support license from Oracle. It is widely used in enterprises, and it is updated regularly.
Impressive. Every word in that paragraph was wrong. well, except the last line.
>The second biggest use is Apache Spark/Kafka, but with LLMs now, you can pretty much re implement all of that functionality in pure C.
Spark is written in Scala, precisely because distributed systems are best modelled as a set of pure functions with minimal references to state. This is also why part of the reason why it's ascending successor, Polars Cloud, is written in a functional language, Rust, rather than C.
Android development is also increasingly being monopolized by Kotlin, not Java.
KTLO = Keep The Lights On
like the sibling tells, a massive amounts of the enterprice software does runs on java
Weird given how much Oracle has bet on AI, both in terms of data centres and in terms of layoffs.
The irony is not lost there. But at least some department there has see the light apparently
People behind JVM are very talented.
Makes sense, there's some precedent that AI generated code is not copyrightable, it's essentially in the public domain for now.
Oracle likes its licenses.
Some important context - it appears it applies to submissions from the community but possibly not to core developers:
> Contributions in the OpenJDK Community must not include content generated, in part or in full, by large language models
So this likely falls more into the category of the inability of the core maintainers to manage the voluminous submissions coming from community than some broad ban of use in AI to develop it at all.
From the page https://openjdk.org/legal/ai -
"6 Is it okay to continue using the spell-checking, grammar-checking, auto-completion, and refactoring features in my editor or IDE?
Yes, so long as they are not based on large language models or similar deep-learning systems."
Banning Ai generated code is like telling people don’t look on stack overflow. I get the idea but it’s a blunt tool to that doesn’t solve the right problem.
Looks like they're stuck between their shady AI dealings and their shady IP dealings.
sips tea
It’ll be a licensing/copywrite concern. Large corporations using GenAI have guardrails and indemnity from their providers to protect them. Taking external contributions is more problematic, at the moment at least. So, in a standard lawyerly manner they shut it down until safe to do so.
Would Cursor tab assisted code be considered AI generated? I feel like that was the epitome of AI assisted but quality code
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.
It's hardly a surprise to see a behemoth like Oracle doing this. Accepting LLM contributions can only be a liability, particularly for such a mature, stable project. Even if you see that liability as small or insignificant, it's non-zero. Given the project and the company, choosing zero additional liability seems like the obvious choice.
One also assumes the people maintaining OpenJDK have had their workload increase to an unmanageable level, like a lot of other free software projects and one thing I'm sure everyone can agree on is that Oracle certainly won't want to pay anyone more or hire more people to deal with that.
A lot of people (including the Register[0]) are pointing out that Oracle leadership are gung-ho about using LLMs for everything, and this seems to go against that. It makes sense to question this from a journalistic angle -- the executives are obviously full of shit and people would do well to remember that the next time one of them opens their mouth. But pointing at the apparent contradiction -- different rules for internal projects vs. open ones -- doesn't seem particularly meaningful on its own:
I don't think the CEO/CTO raving about LLMs should be taken as firm statements about how they actually operate internally. I'm surprised that this does not seem to be the default case. Among other things, Oracle stands to profit from greater adoption of LLM tools.
It would be unrealistic/unreasonable to expect their employees/contractors working on internal projects to be held to the same standard/guidelines/rules as developers contributing to a free software project. This applies either way, whichever side (internal/open) has the worse deal.
I don't know what the rules are for their internal teams. As far as I know, I'm not alone in that. Oracle also don't need to post anything publicly to change those rules.
[0] https://www.theregister.com/ai-and-ml/2026/08/03/as-larry-el...
Rules for thee, but not for me. well I don't expect better from tech companies now.
Never forget: AI is for peons.
https://openjdk.org/legal/ai
I don't think this is as big of news as it needs to be. The explanations are from a risk-management perspective.
While the Oracle hate boils, Zig, Rust,... aren't much different.
There is also the approach of Microsoft putting AI all over the place on .NET, and CoPilot driven development all over the place.
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.
How does all this AI generated code blocking gappen? Does a human decide that or an AI is tasked with sequencing that PR's DNA to ascertain its possible inhuman origins?
What if someone generates code with AI and then goes into the IDE and then bathes it, dresses it (including adding comments) etc, in a way a human would? What then? No, here I am not exploring a way to fool the code DNA checking, but rather trying to find out what the real problem is with the AI generated code? (Other than license issues, too many PRs etc)
The FAQ addresses these questions: https://openjdk.org/legal/ai
There is a more helpful way to reply, that includes this text.
I believe in linking over copy & paste, in particular when I want neither to quote the full FAQ nor editorialize by selective quoting. By reading the FAQ, people can form their own opinion on it.
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? Yes? No. 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 at the beach instead of trying to trick a project that is politely asking you not to trick it!
This is a friendly reminder from a grouchy old fart that
1. You are the engineer of record on all of your commits.
2. As the engineer of record, you have a certain duty of care with regards to code quality.
3. If you are not signing your commits, you are not providing reasonable provenance and instead tossing your name around in a way that anyone can replicate with impunity.
https://openjdk.org/legal/ai
Shitposting, the reasons are very clear and explicit: The risks of having legal problems are very clear.
Google for example GEMA vs. OpenAI.
Oracle bans AI code from OpenJDK but I'm fairly sure the release notes have been written by a model for a year now.
How could we know whether incoming code is AI generated or not? are there tools for this?
If they had a policy to ban German speakers from submitting code to OpenJDK, it would have the same effect. None at all, which is maybe the point. It's another tool to categorize submissions/submitters they find problematic.
"If I don't know you, I don't merge you"
And if you catch somebody submitting code they can't explain, you don't know them anymore.
It's really simple. Open source has always had a social layer. Github culture tries to eliminate it, and that's the source of this vulnerability.
First thought I had too. I deliberately strip AI metadata from my PRs in certain orgs.
Why not just write the code yourself? You sound like an addict hiding their use from their friends and family.
First time you're caught, you are no longer a project contributor and your deceptive conduct will be forwarded to all other major open source projects with warnings that your code cannot be trustworthy and is a well documented legal liability. How's that sit with you?
This is inherently deceptive.
AI is for people who are proud of their obduracy.
This is the firm whose debt is one level above junk and whose survival as a single unbroken corporate entity is fully predicated on OpenAI being able to make money from the data centres they (Oracle) are building for them, let alone simply paying for them.
I accept @jerf's explanation is the right one but this is an absolutely almighty signal that AI-first developers should heed. And someone should ask Altman about it on the record.
I don't think you should take "AI-first developers" seriously as a category.
The people you refer to are delusional idiots and should be treated as such.
I don't disagree. But at the moment it is ~all major tech CEOs, right? Companies everywhere are saying "increasingly we don't write our own code". Out loud in front of their investors and customers. Even Oracle did.
But people at Oracle below the C suite don't even fart in public without lawyers signing off.
This is Oracle telling quite a lot of customers and partners of one of their most significant products that it doesn't trust AI code to be safe. Oracle, the company that is more exposed to the bubble bursting than basically anyone else apart from Coreweave.
This message could have been a lot shorter, could have said they were pausing accepting AI submissions until the intellectual property situation was clarified, but no — they said AI code can be unsafe and insecure and it's too risky to accept it. So a good question (given that Oracle are fucked if OpenAI even stumbles) is why?
That is a heck of a message to send, and it is visible enough. That is why I think developers (by which I mean individuals and their companies) whose focus is AI-generated code, which is almost everyone in public, should pay a bit of attention.
"AI-generated code" will become shorthand for code-that-wasn't-verified-and-organized-by-a-competent-human.
AI for me but not for thee.
How would they even be able to tell the difference?
So Java, which powers a sizeable chunk of the real-world since two decades now, without needing the help of LLMish sloppy-pasta, is going to continue to power the Real World [TM] with its language and JVM that have been created with tens of millions of human man-hours without LLMish sloppy-pasta?
I'm shocked.
I'm not only shocked: I also see there a delicious irony in the countless of LLMish sloppy-pasta code that's now running and going to be run on man-made JVMs.
Closer to three decades than two.
> 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.
If you asked the LLM to create an Android app it probably would.
Interesting idea, so I had to check!
Prompt: “Top language pick for an Android app? Respond with only the language.”
Responses (admittedly via the aichat CLI, not an agent harness; and temp=0):
Kimi K3: Kotlin
GPT 5.6 Sol: Kotlin
Claude Fable 5: Kotlin
DeepSeek v4 Flash 0731: Kotlin
Are there any other “inherently” heavily JVM-biased domains?
I think even in Minecraft game mods Kotlin is possible nowadays…
Kotlin my dude, unless you hate yourself.
Linus might want to look over Oracle's reasoning and reconsider the potential legal harm that can come to the Linux kernel from accepting AI code.
How do you even enforce such policy?
How is this enforceable?
Deeply ironic.
I would laugh for a week if the courts eventually found issues with using LLM content and forced companies to either publish their LLM generated code as public domain or they were forced to roll back their codebases to a pre-LLM state.
Probably won’t happen but clearly Oracle sees a potential for legal issues with LLM output.
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.
BREAKING Oracle pretends to be technical as we enter a new era where managers and corporate slobs larp as geniuses
So they will not be accepting most security patches. Fun.
Oracle is just selling AI shovels. Of course it would have a hard time defending IP issues in slop code when it had famously sued Google for Java infringement.
Also, Oracle knows that it will be stronger with strong IP laws. Other companies will realize that fact soon.
It's not Oracle that issued the ban -- it doesn't have that authority. It's the OpenJDK Governing Board. (Of course the latter generally follows Oracle's lead.)
https://openjdk.org/legal/ai
That Oracle's policies over its internal code base are different is irrelevant.
Fascinating coming from a company hurting so hard from their over-leveraged positions in AI.
[dupe] Discussion: https://news.ycombinator.com/item?id=49109165
Imagine Oracle suing themselves due to licensed use violations; can't have that!!!
They just have their panties in a bunch because that one guy on Youtube said they'd be the first domino to fall in the AIpocalypse. https://www.youtube.com/watch?v=py23zYn1GMw
great now we will have slop , just not vibed slop
ORACLE???
Not long ago it seemed as if AI Skynet is winning the war.
Now slowly, the Empire strikes back - not just Oracle, but more and more resist the tyranny of AI skynet slop.
I am upset that these corporations drove up the RAM prices still. They need to compensate the rest of mankind for this - after all the chip market is a de-facto monopoly. They should all be sued into nothingness, then new laws must enforce healthy and fair competition, without unfair players driving up the prices willy-nilly style. Absolute AI mafia here.
lmao
Oracle is not a software company, but a litigation company. It will be hard to sue people because LLMs generated code similar to some code copyrighted by Oracle if they themselves use LLMs internally to generate code.
Hilarious thing is, if I want a JDK, I'll ask Fable to write one, get Sol to review it and write tests for it, and it will be working by Monday morning. No need to get permission or anything else from Oracle. Building a complex product from many smaller, individually-testable components is exactly what LLMs are good at, and a Java SDK certainly qualifies.
And if I run out of tokens, well, that's OK too. K3 running on my own box will finish the job. I'll just have to wait another week, that's all.
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?
Excellent point. Why, indeed.
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.
Never get high on your own supply, says the dope peddler.
What happens to OpenJDK when Oracle dies? That's looking increasingly likely on a 3-5yr horizon.
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 would expect it to be picked up by the Eclipse Foundation. They already have the Java Ent- I mean, Jakarta Enterprise Edition.
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
The same that happened when Sun died: it gets bought by someone else.
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.
Policies like this will result in the death of the branded software.
As we move forward it will be easier than ever to just maintain and keep your fork of software with the changes you want or need. No more approval, bureaucracy, or arguing. Just tell the AI agent want you want changed and you have it.
This will be used for huge things too. Like maybe you want a specific fork of Java that only supports for each iterators, goodby linters, hello compile time error.
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 do.
Software as a list of requirements and that's it. The local LLM appliance everybody has taking in a document specifying hardware, interfaces, and requirements and spitting out software changeable locally via conversation with its users.
In the same way you have a cookbook with recipes to make dinner instead of ordering out.
> Software as a list of requirements and that's it. [...] a document specifying hardware, interfaces, and requirements [...]
For that, you'd want the list of requirements and hardware documentation to be written in a precise, formal language. That's no different than writing them in a programming language (though a declarative one, instead of the more common imperative ones).
I've in the past (way before LLMs existed) thought about automatically generating device drivers from hardware documentation. But besides the need for very precise documentation, hardware never works exactly as documented; a human-written device driver can avoid problematic areas (perhaps even by accident), while a computer-written device driver would end up exploiting every corner case of the documentation.
> For that, you'd want the list of requirements and hardware documentation to be written in a precise, formal language. That's no different than writing them in a programming language (though a declarative one, instead of the more common imperative ones).
From my perspective, this is a damning conclusion to the argument.
That being said, I can hear him asking Claude to generate a rebuttal as we speak.
Requirements ARE written in a precise, formal language. These days most people don't actually have any contact at all with real requirements though as practiced by professionals.
There is quite a bit of distance between the exactness of any human language and an sort of programming languages. When you have a language model loaded with software engineering best practices you do not need the exactness of a programming language to describe desired behavior.
Hardware documentation is indeed often lacking in plenty of ways but in a world where writing your own software through agents is commonplace, the hardware manufacturers (or the community) would make testing that documentation to find the problems an important part of hardware development.
Most people don't bake their own bread even if it's more approachable, and cheaper then vibecoding. Bread is just a recipe one may say. But in modern times have we ever witnessed disappearance of specialization? I don't think so.
That is a cool perspective to consider.
> 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.
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.
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.
> 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.
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.
This is far more likely to happen in a corporate setting with competent engineers who want to build/solve now versus relying on others. I've seen it 100% of the time with varying results.
The idea of someone forking Java with vibe code nonsense and expecting them to be able to maintain is laughable.
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.
Given how much of the industry is SaaS that would be such a self own! Wow, fantastic, you can build all your software in house, zero dependencies. Wait, your users can do the same? And they don’t need to pay you anymore for any of your cool services because they just asked their agents to recreate your infra from scratch? Interesting, truly the future of humanity
> Wow, fantastic, you can build all your software in house, zero dependencies. Wait, your users can do the same? And they don’t need to pay you anymore for any of your cool services because they just asked their agents to recreate your infra from scratch?
The cherry on top is that OpenAI and Anthropic brainwashed your coworkers and your company's C-suite into uploading the entirety of the "proprietary" codebase onto their servers thousands of times per day over the last three years.
No need to brainwash, they did it willingly and with a smile, tweeting about how they are part of the revolution while telling us all how we will be left behind
Relevant xkcd: https://xkcd.com/605/
LOL
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.
> 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
Because SQLite has 10k requirements that wouldn't even cross your mind to write down, but 80% of which are useful to you.
The nice thing about natural language is that nesting semantic layers is free and arbitrary, and far more tractable than in a formal grammar. Every natural language is like coherentist ω-order logic. Effectively, I don't have to write the 10k requirements. I only need to provide a sufficient metatheory that can be extrapolatable to those 10k requirements, and that can include embedded theory I did not write myself but am familiar with enough to invoke, as well as refinement criteria ranging from the fuzzy to the explicit with priority weighting parameters to describe the shape in which I want the search space pruned.
This isn't anything new or particularly interesting. It's the entire basis upon which ILP demonstrated generality. A metatheory to synthesize 10 trillion rules isn't even scratching the surface of what you can reasonably do. The key was finding out the tractable semantics for actually computing it in reasonable amount of time, which right now is looking decidedly like informal semantics was the answer the whole time.
Not sure what this is a parody of, but it's hilarious, thank you. Keep it up!
I accept your concession. The humiliation of irrationally committed foundationalists has been a long time coming, so it's good you're trying to get ahead of the curve.
>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
https://www.youtube.com/watch?v=V_qzqY1bb7I your sufficiently advanced code generator may generate you a high quality database system for some measure of quality, but it will not have SQLite's reliability over the extremely long tail of edge cases proven through its testing and use in real life
Then you've failed the criteria of sufficiently advanced. It's perfectly fine to cast doubt we'll see scaling to this generalization, but you're not casting doubt you're outright rejecting the premise in-confidence. It betrays that you have no idea what you're talking about. May I see your quantification of this long tail? Do you even know how to formalize the mapping from n-bit precision of weights and/or activations to the standard deviation of a transformer's output distribution, such that we could decide whether the long tail of a given behavior is unreachable? Something tells me that no, you don't know how to do that in the slightest. So what drives you to speak with such confidence?
That's before we get into the entire non-linearity of agentic systems introducing massive decidability problems on this in the first place. A little bit of epistemic humility please.
You still spend all your time troubleshooting the reinvented wheels even if AI writes it because you won’t know the edge cases til you hit them. Then you modify the lib, re-release, and update all your apps, but now look where all your time is spent.
The assumption you make is the classic LLM mistake of thinking writing code === building software.
To cite your example SQL has had its tires kicked a lot it’s seen things you can’t even imagine thanks to being used millions of times by millions of people. It’s hard to just replicate all that iteration, learning, mastery, and process. If you reinvent it, users will encounter the dumbest bugs over and over and over. Sure you’ll fix them, but you’re now embarking on this big thing that SQL and others already did.
If you love the problem space definitely do it - go full steam ahead - especially if you’re actually innovating and doing things better, but don’t be fooled into thinking anyone can, or should with every side project.
The new struggle is focus, what not to build, I almost have the purely opposite view of instead of using LLMs for grandiosity, only using the LLM for tedium and making sure it doesn’t do anything too much that I haven’t planned for or want to do. I drive the thing, so every new project is still my time and energy and focus.