Hacker News new | ask | show | jobs
by saurik 1138 days ago
I mean, if you--as a human--read that code yourself, learned how it worked, and then tried to write something similar later--even in a different programming language!--that is highly likely to be contaminated and considered a derivative work <- this is the reason why clean room design--where you have one team look at the original to write documentation which is then cleared by a lawyer to not contain any expressive intent before being handed to a second disjoint team to implement--is a thing people have to do. That GitHub Copilot is somehow afforded some kind magic assumption that it perfectly removes expressive intent is kind of ridiculous and highly unfortunate.
1 comments

I find it terrifying that this type of reasoning is actually legitimate law.

Think about all the drive by licensing felonies everyone has comitted by accidentally reading open core code and then, at a later point implementing something vaguely related....

EDIT: Typos & punctuation

IANAL but that's why law has to be interpreted by judges rather than being a book of absolute rules.

Lots of codified laws are bent or modified by prevailing social attitudes, customs or precedent, so you could argue "I looked at it a couple of years ago and then independently decided to implement something similar" is a very different situation to "we read through the code and a week later started on a competitor".

Whether you'd get away with it is another matter, depending upon interpretation and perspective.

The clean room described above is a fairly bullet proof technique, but it's only been employed very few times and is not necessary to create an original work. Nearly every work was produced by people who were exposed to other copyrighted works. Unless something is a straightforward copy, it's a high burden to show that something is effectively a copy or translation. A lot of these kinds of things are untested in court probably because it's so difficult to make an abstract case.