155
submitted 2 weeks ago by cm0002@lemy.lol to c/linux@programming.dev
you are viewing a single comment's thread
view the rest of the comments
[-] RickyRigatoni@piefed.zip 81 points 2 weeks ago

All it takes is one person using an LLM tainted with proprietary code which then just gives them that code line for line to undo decades of courtroom defense.

[-] black0ut@pawb.social 45 points 2 weeks ago* (last edited 2 weeks ago)

Not only that, but AI output can't be licensed/copyrighted. The GPL license no longer covers the kernel in legal terms.

[-] Franconian_Nomad@feddit.org 11 points 2 weeks ago

There seems to be legal discussions about that. It’s not quite as simple as you say:

However, there may be cases in which a different assessment is justified, namely when users use and operate the LLM as a tool that merely implements their personal creative intent. This could be compared somewhat more vividly to using a paintbrush. If the brush merely rolls over the paper, for example because it is dropped, no copyright-protected work is created, even if paint remains on the paper. However, if a painter deliberately swings the brush in a certain way, a protected painting can be created. If AI is used in a comparable way a copyright-protected work can indeed be created.

https://kpmg-law.de/en/ai-and-copyright-what-is-permitted-when-using-llms/

[-] The_Decryptor@aussie.zone 12 points 2 weeks ago

Yeah any decision would be on a case by case basis, which is normally something you'd want to avoid.

I've seen a couple of Linux devs talk about how they just give a prompt to claude and walk away leaving it alone to spit out the code, none of which can be licensed as GPL. But good luck working out what specific lines of what specific patches of theirs used an LLM vs. were re-written or such.

[-] Franconian_Nomad@feddit.org 6 points 2 weeks ago

I've seen a couple of Linux devs talk about how they just give a prompt to claude and walk away leaving it alone to spit out the code

While I share Linus opinion on LLMs, I think doing this shit is extremely stupid and lazy.

[-] SirActionSack@aussie.zone 6 points 1 week ago* (last edited 1 week ago)

Best to not believe anything KPMG says about AI.

Actually if KPMG say the sky is blue you should probably go outside and check and also make sure you still have your wallet.

[-] fogetaboutit@programming.dev 3 points 1 week ago

yeah and the paintbrush somehow has abstracted access to millions of proprietary and copyleft licensed source code in forms of weight.

this is a clear misuse and abuse of any fair use rights, and clear push to centralisation of copyright to only a few companies with big budgets that can defend themselves.

i mean, can you really challenge and win against openai, a company backed by the govt, that your copyleft source code are misused as training data?

[-] terabyterex@lemmy.world 4 points 1 week ago

this is FUD and not true. projects are licensed not lines of code.

[-] victorz@lemmy.world 5 points 1 week ago

But if there are proprietary lines of code that end up in a project with an open license, you get a violation. 🤷‍♂️

[-] terabyterex@lemmy.world 4 points 1 week ago

what is a proprietary line of code? how do you look at a for loop or uf statement and say "i own that". i can tell you that in all the huge applications i have worked on in the last 27 years, there isnt special proprietary code. there is proprietary data but not code.

the only time you really have proprietary codeis specialized code talking to a specialized device. so maybe a closed source driver.

[-] victorz@lemmy.world 6 points 1 week ago* (last edited 1 week ago)

I have worked at two companies back-to-back for a total of about 8 years, so significantly less time, that both definitely had proprietary code.

It is code that does things that nobody else is doing, or able to do, and patented, I believe(?).

But nice anecdote. 👍

[-] Franconian_Nomad@feddit.org 4 points 2 weeks ago

Ist that a common thing that LLMs using proprietary code for coding tasks?

Because I don’t think so.

[-] gjoel@programming.dev 11 points 2 weeks ago

They use everything for everything, that's the big issue. Also gpl code. Anything they can trawl through they use. And replicate, in part or in full.

[-] Franconian_Nomad@feddit.org 1 points 2 weeks ago

They take code snippets and copy and paste them? Or do they create own code based on what they’ve learned by trawling?

[-] Barbarian@sh.itjust.works 16 points 2 weeks ago* (last edited 2 weeks ago)

LLMs don't "create". Under the hood, they're tokenizing the queries, looking for "clouds" of tokens that are similar to the query, then returning a sequence of tokens (with some random noise thrown in) that match what their training data says the answer should be.

In short: all LLM code is an amalgamation of their training data by definition. If there's nothing similar in there, it's literally not possible for it to be part of any response.

[-] Franconian_Nomad@feddit.org 3 points 2 weeks ago

You’re exactly right. I should have used „generate“ instead of „create“.The point is I don’t think LLMs normally use copyrighted code in a way that would hurt open source projects.

Under the hood, they're tokenizing the queries, looking for "clouds" of tokens that are similar to the query, then returning a sequence of tokens (with some random noise thrown in) that match what their training data says the answer should be.

Lol, so how do humans code in comparison?

[-] prole 6 points 2 weeks ago

You’re exactly right. I should have used „generate“ instead of „create“

Did you purposely respond like an AI?

[-] Franconian_Nomad@feddit.org 3 points 1 week ago

Damn, I forgot the em dash.

[-] Barbarian@sh.itjust.works 4 points 2 weeks ago* (last edited 2 weeks ago)

The point is I don’t think LLMs normally use copyrighted code in a way that would hurt open source projects.

I don't know. I'm not a lawyer, and copyright for code was a hot mess even before LLMs got involved. With how many opportunistic copyright/patent trolls there are and how easily convinced judges have been in the past, it could go either way.

Lol, so how do humans code in comparison?

The good programmers normally code by breaking down the problem into constituent parts and logically working through the problem, step by step. What differentiates this from tokenization is that instead of just looking for code that is similar for a similar problem, programmers can usually understand the effects of each line of code, visualize what the state of each variable will be in that step (or dump out the variables to look directly if unsure), and then move on to the next step. This logical problem-solving approach is fundamentally different from a tokenization+noise looking for a similar-looking problem approach. For one thing, you can solve problems that haven't been solved before.

[-] vanillama@programming.dev 3 points 2 weeks ago

Human programmers at least can tell you where they got a snippet they copied, whether it was in the docs, stack overflow or elsewhere, and you can try to keep attribution if you care about compliance. Not only that, but most of our skills are related to designing stuff and recognizing which pattern to use, the specific implementation isn't necessary the same unless we go look for whatever we saw in the past, as our memories don't just record everything and repeat it word by word. And after picking up a new language or framework I only need to look around when using a third party library or some API I'm less familiar with, or when something breaks.

[-] SirActionSack@aussie.zone 2 points 1 week ago

What do you think the LLM is using for reference when generating code? It can't create from nothing.

[-] ikidd@lemmy.dbzer0.com 2 points 1 week ago

Yah, before AI there's never been a chance of proprietary code entering the Linux ecosystem and they have no defences against it at all.

this post was submitted on 16 Jul 2026
155 points (100.0% liked)

Linux

14476 readers
489 users here now

A community for everything relating to the GNU/Linux operating system (except the memes!)

Also, check out:

Original icon base courtesy of lewing@isc.tamu.edu and The GIMP

founded 3 years ago
MODERATORS