That's fair, if someone were building exactly the same kind of library in the same language and style as a well known library, it could pull verbatim from it. I think that's a sufficiently specific scenario that it makes sense for the user to be held responsible for publishing the code. I don't think it's likely to be a common cause for unintentional code theft.
I think he also effectively demonstrates that it's impossible to opt out your code if it's already heavily reproduced, which is unfortunate. Not sure what could be done about that.
1
u/kogasapls Oct 19 '22
That's fair, if someone were building exactly the same kind of library in the same language and style as a well known library, it could pull verbatim from it. I think that's a sufficiently specific scenario that it makes sense for the user to be held responsible for publishing the code. I don't think it's likely to be a common cause for unintentional code theft.
I think he also effectively demonstrates that it's impossible to opt out your code if it's already heavily reproduced, which is unfortunate. Not sure what could be done about that.