![](/static/253f0d9b/assets/icons/icon-96x96.png)
![](https://programming.dev/pictrs/image/8140dda6-9512-4297-ac17-d303638c90a6.png)
The judge also noted that the cited study itself mentions that GitHub Copilot “rarely emits memorised code in benign situations.”
“Rarely” is not zero. This looks like it’s opening a loophole to copying open source code with strong copyleft licenses like the GPL:
- Find OSS code you want to copy
- Set up conditions for Copilot to reproduce code
- Copy code into your commercial product
- When sued, just claim Copilot generated the code
Depending on how good your lawyers are, 2 is optional. And bingo! All the OSS code you want without those pesky restrictive licenses.
In fact, I wonder if there’s a way to automate step 2. Some way to analyze an OSS GitHub repo to generate inputs for Copilot that will then regurgitate that same repo.
What I consistently don’t see brought up is the fact that the “chaotic withdrawal” was directly set up by Trump. He signed the agreement with Afghanistan that put a fixed date on the withdrawal squarely in the next President’s term. This gave enemies a clear timetable of US actions beforehand, which gave them a significant advantage. So Biden was left with the choice of either fulfilling the US promise, despite it being in every way a bad construct, and executing an extremely difficult withdrawal, or harming the US image on the global stage by reneging on an already agreed upon deal.
I would go so far as to say this, like the expiration of the middle class portion of the Trump tax cuts, was specifically designed to make the next administration, which was always very likely to be Democrat, look bad regardless of the cost or collateral damage.