News for hackers. Stuff that matters.
Re:60x speed-up of Linux “perf” by matheusmoreira on Thursday September 09, 2021 @12:13PM (#28471296)
> carefully avoiding making the code too similar to what I happen to remember

Is this really necessary? The GPL allows you to read and study the software. Is it really copyright infringement if you take your understanding and make your own program? Are people really forced to come up with convoluted new ways to solve the same problem just to avoid any similarity to existing work?

Re:60x speed-up of Linux “perf” by Salgat on Thursday September 09, 2021 @12:39PM (#28471622)
The issue is that the only way to guarantee no liability is a clean room implementation. It's why most open source reimplementations require no mention or examination of the source/machine code. Google got dinged over a trivial method they copied in their java implementation, even though it was extremely trivial. You can't risk any chance of copying, regardless of how trivial the code.
Re:60x speed-up of Linux “perf” by MaulingMonkey on Thursday September 09, 2021 @02:07PM (#28472728)
Patent and copyright trolls have shown that even a clean room implementation is no guarantee.
Re:60x speed-up of Linux “perf” by Salgat on Thursday September 09, 2021 @05:22PM (#28474822)
True, but at least you as the employee won't get fired since you can't be blamed.
Re:60x speed-up of Linux “perf” by kmeisthax on Thursday September 09, 2021 @03:40PM (#28473773)
No, what you're describing is not itself copyright infringement. There are actually two legal standards for infringement in the US:

- Striking similarity, or what most of us think of as infringement, where there's literal copies of someone else's code in your own. This is what things like content ID systems try to detect.

- Access plus substantial similarity. This is where you've looked at someone else's code (source or disassembled, doesn't really matter); and then produced something that looks a lot like that code if you squint a little.

Substantial similarity does not have a hard-and-fast rule associated with it, it's usually something that juries or judges decide. It's basically the "yeah just change it a little so the teacher doesn't notice" meme, but in legal form. If you were to read another program's code, and then make another program that looked an awful lot like the first, then you'd be infringing. But this is bounded by other exceptions to and rules of copyright - notably, functionality itself can't be copyrighted, and copyright over interfaces is largely prescribed by various fair use decisions (so emulation and re-implementation is largely still OK even under this standard).

If you read GCC, and then write LLVM, that's not substantial similarity. That's a different, legally distinct compiler design. The FSF could sue the pants off Apple if merely reading GCC source meant any compiler you wrote was infringing.

If you read GCC, and then write a compiler with the same internal representation as GCC; a parser that's structured the same way as GCC; and optimization passes that are organized the same way as GCC's; then you're closer to infringing.

Your responsibility isn't to create an entirely novel program by any means necessary. It's just to avoid doing the software equivalent of tracing over someone else's drawing.

Re:60x speed-up of Linux “perf” by toast0 on Thursday September 09, 2021 @12:43PM (#28471670)
It depends on what derivative work means, and finding out the specifics may mean spending time in court.

GPLv3 says 'To “modify” a work means to copy from or adapt all or part of the work in a fashion requiring copyright permission, other than the making of an exact copy. The resulting work is called a “modified version” of the earlier work or a work “based on” the earlier work.'

If you read and study a work, and then write something new that does the same thing, that may be considered adapting or copying from (parts of) the original work.

Re:60x speed-up of Linux “perf” by Dylan16807 on Thursday September 09, 2021 @06:33PM (#28475452)
"in a fashion requiring copyright permission" is basically the definition of "derivative" here, so the GPL is rightfully farming that question out to external law and not even trying to tell you the answer.
Re:60x speed-up of Linux “perf” by nonbirithm on Thursday September 09, 2021 @12:50PM (#28471774)
What I wasn't sure of is, as long as I never actually incorporate the original code, if basing your fundamental design on something counts as infringement. I find it hard to see the difference between taking some class definitions and changing the variable names and going off to use what you learned from other people only to realize you arrived at the same design as they did because doing anything else would mean the implementation would be worse than what you now know it could be.

I don't have much of an understanding of copyright when it comes to cases like those, but my worry is that declaring that your open-source codebase is merely inspired by codebase X with this specific code in the case of these specific data structures would still count as infringement in a court of law. However, I don't intend to infringe on the licenses of the original, and do not intend to directly copy any code.

Re:60x speed-up of Linux “perf” by troutwine on Thursday September 09, 2021 @12:58PM (#28471855)
Dunno! For what it's worth I build a lot of MIT and MPL software professionally and the lawyers at several employers have suggested doing exactly what the GP does. My assumption has been that proving derivation in a court is an expensive process however it turns out, so why risk it.
Re:60x speed-up of Linux “perf” by jdavis703 on Thursday September 09, 2021 @12:40PM (#28471632)
Think about it this way. If a panel of jurists who only half understood the expert testimony saw your code side by side with other code would it look like blatant copying or not?