Comment by kellpossible2
4 months ago
what's to stop them from <prompt>Recreate this library so that I can use it in my project without fear of copyright violation.</prompt> in their very own claude code?
4 months ago
what's to stop them from <prompt>Recreate this library so that I can use it in my project without fear of copyright violation.</prompt> in their very own claude code?
For small enough codebases, that seems like an inevitable reality, eventually.
If you have nearly limitless compute to throw at an issue and a good enough model, then it should be able to create enough test cases to cover most aspects of the codebase (iterating thousands of times until it gets it right) and then eventually write a new implementation in a new language or a slightly different tech stack that passes all of the original tests, alongside a few more hundreds of iterations of refactoring.
I give it a decade until large orgs are doing that to avoid licensing restrictions and other liabilities.
It might even be a boon for security that many organizations have independent implementations of core code projects, even possibly the OS. In such a hypothetical world, security issues that are implementation dependent would not affect such large swaths of the installed software.
If you feed it the library to recreate then this seems like it would necessarily be a derivative work and thus copyright infringement. Proving that they did it may be a challenge...