NetBSD still has an edge with its memory hardening, NPF, kernel-level blacklist, and “legacy support”. But I fear that this out-of-touch policy might eventually tip it into irrelevance.
The BSDs were burned by this in the 4.4BSD days.[1] It makes sense that they don’t want to be burned again.
[1] https://en.wikipedia.org/wiki/UNIX_System_Laboratories,_Inc.....
The most advanced tools were template based generators and real-time static checkers plus language servers. AI makes things way more complicated than it is.
It's not only bleed of GPL into MIT. It's also bleeding of source-available licensed corpus to AI models. These things leak their training data like crazy. Ask the right question and get functions from training sets verbatim.
When everything is combined, this is a huge problem. It's not that these problems are individually OK. They're huge already. The resulting problem is a sum of huge problems.
There are GPL projects which provide people their livelihoods, because they get grants to develop that code with a GPL license. Ingesting the same code to a model sans it’s license not only infringes on the license, but allows this code to seep to places where it shouldn’t (by design), and puts this man’s livelihood in jeopardy.
Companies frowned upon GPL for years because of its liability, and now they can feast over this code with these models.
Same is for source available repositories. These companies put their code out for eyes only, not for reproduction and introduction to other code bases. These systems also infringe on these licenses, and attacking to the business models of these companies.
I’m not a copyright stickler. I just respect people and their choices they made with their code.
P.S.: I can share the tweets of that researcher if you want.
It is CC-BY-SA so it requires attribution (+ share alike).[1] That is the hard part with code written by LLMs.
Update: SA 4.0 accepts GPLv3 as compatible, and I use GPLv3 exclusively. I'm on clear.
LLMs neither know provenance nor licenses about the things they generate, you're right. I think that part of the problem is ignored not just because it's hard, but it's convenient to ignore, too.
I doubt this genericism applies to codebases the like of the *BSD's, or the linux kernel.
I also think SO is different about mindless copy-pasting. Outside of rote beginner stuff it’s infrequent that someone has the exact same question as you, and that the best answer works by simple copy-pasting. Often the modification is simple enough that even GPT can do it :) But making sure the SO question is relevant, and modifying the answer accordingly, is a check on understanding that LLMs don’t really have. In particular, a SO answer might be “wildly wrong” syntactically but essentially correct semantically. LLMs can give you the exact opposite problem.
> DENSE_RANK() OVER (ORDER BY TotalMark DESC) AS StudRank
And then I filled in my column names and alias. This is 90% of what is happening with LLMs / SO copying. Copy / paste of syntax like this absolutely does not need a link or attribution and is in no way copyrightable in the first place.
Case in point: https://x.com/docsparse/status/1581461734665367554
This is not akin to copying a 2-line trick from SO.
On the other hand, the most significant part of code I copied from SO was using two iostream iterators to automatically tokenize an incoming string. 5-6 lines at most.
This block has a 10+ line comment on top of it not only explaining how it works, but it has a link to the original answer at SO.
... doesn't say automatic copying.