3 ms·
The simplest way to mitigate the risk that you might be sued if your code is too similar to someone else's code is not to share it openly in the first place. If
by onion2k 11y ago
The simplest way to mitigate the risk that you might be sued if your code is too similar to someone else's code is not to share it openly in the first place. If Oracle win then every large corporation will have to ask the question "Can we release our code? Do we know it's all ours and not something a developer took from a closed project[1]?". Many will choose to not to because the risk is too high.
[1] Knowingly or otherwise. If a dev bases their code on a Stackover Flow answer they could be unwittingly using closed code.
- nunobrito 11y agoSafety by obscurity might not be a magic bullet. I'd still be able to tell much just from the compiled binaries. For example, I wouldn't detect your code snippets from stackoverflow but would be capable of creating a very comprehensive list of third-party dependencies you are using. There are companies completely dedicated to the software originality topic: http://triplecheck.net/ http://triplecheck.net/