News for hackers. Stuff that matters.
Re:Coping with Copilot by cmrdporcupine on Saturday August 20, 2022 @04:46PM (#32535030)
I don't care about all the handwaving here, it comes down to this.

The moment a fragment of code from a GPL'd or AGPL'd project shows up almost verbatim in someone's closed source or non-copylefted, etc. project, and someone proves it, sparks are going to fly.

And it's probably already happening, just people haven't discovered it yet.

How many years did the Oracle/Google lawsuit go on for? And in the end about a handful of a lines of code only tangentially related to the issue at hand?

Part of the lesson from that must be: employers should be telling their workers to say TF away from Copilot or things like it. And be careful in general when browsing source. License literacy is critical.

I don't touch it because I need to feed my kids. I don't need my career exploded. Overcautious? Maybe. I'll let someone else find out. I make a living in and around open source software.

Re:Coping with Copilot by bayindirh on Saturday August 20, 2022 @05:12PM (#32535177)
> The moment a fragment of code from a GPL'd or AGPL'd project shows up almost verbatim in someone's closed source or non-copylefted, etc. project, and someone proves it, sparks are going to fly.

I'm hoarding popcorn and can't wait for that, honestly.

> License literacy is critical.

It's beyond critical, but most people I have talked says that they see the right to copy and use any code they see online. They don't care.

Building this open source corpus was not easy, and we need to defend it too. This is a culture.

Re:Coping with Copilot by pabs3 on Sunday August 21, 2022 @01:12AM (#32537574)
Didn't it already happen that it spat out a function from Quake? And they then dealt with that by banning the particular function.

ISTR that Amazon's version of copilot has licensing info output too.