Linked by Thom Holwerda on Thu 28th Oct 2010 20:07 UTC, submitted by poundsmack
Permalink for comment 447507
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 05/18/13 21:06 UTC
Linked by Thom Holwerda on 05/18/13 7:37 UTC
Linked by fran on 05/18/13 1:38 UTC
Linked by Thom Holwerda on 05/17/13 23:35 UTC, submitted by kragil
Linked by MOS6510 on 05/17/13 22:22 UTC
Linked by Thom Holwerda on 05/17/13 22:15 UTC, submitted by Tom
Linked by Thom Holwerda on 05/16/13 21:41 UTC
Linked by Thom Holwerda on 05/16/13 17:04 UTC
Linked by Thom Holwerda on 05/16/13 13:17 UTC
Linked by Thom Holwerda on 05/16/13 12:06 UTC
More News »
Sponsored Links



Member since:
2009-06-18
While not commenting in anyway on the allegations, I will say that this is really hard to track in practice.
How would you know if it was a copy unless you saw the original?
I can say from experience working on these kind of projects, I often go out of my way never to see the original.
Perhaps automated mechanisms might be put in place if you were doing a really high-profile project like Harmony. Apache might have setup some diff against the JDK to double check that no one brought in suspicious code (not nearly as simple to do as it sounds...); but was it OSS when they started Harmony though? I don't think it was...
At the end of the day, it is just hard to know if the code you are getting has been taken from some other code, somewhere else you don't know about.
Short version is that it is hard enough to know all your own code; knowing all of everyone else's code is plain impossible.
Edited 2010-10-28 21:16 UTC