On discussing clones
Posted: Sat Feb 21, 2009 5:15 pm
If the general feeling here is that discussing clones is a no-no here, then I am more than willing to take my discussions back to r.g.c.c where while we have to live with excessive noise, we don't have to live with excessive "thought police" running around.
The "no libel" idea is a crock, and is just an excuse to avoid discussing a specific topic that nobody likes. Namely the Rybka came from Fruit discussion. I have my own thoughts which primarily leads me to conclude that there is way to much similarity to be purely based on random chance. I have looked at several open-source programs and never found duplicated piece/square table values as an example. But I'll admit that it is possible to come up with the same values independently, if you think flipping 1,000 heads in a row is something that won't take years at least. It is possible that two different programmers would use the same odd constructs. About the same again as 1,000 heads in a row. But both together? Now it is like 1,000,000 heads in a row.
Regardless of what is done in Rybka of today, R1 _clearly_ has significant parts of fruit included. That's old news. Those that want absolute proof know that such is impossible when anyone can write a 10 line program that will, given enough time, produce source code that is identical with fruit. The fact that this might take a few billion years to happen is not important to them. And given that, absolute proof is not possible. Fortunately, in most court systems, it is not necessary to have a video showing the crime being committed and with a clear facial image of the accused.
Trying to suppress such discussions is a sign of several problems:
(1) "author XXX" can't possibly have copied his program. It is stronger than what was supposedly copied. Argument is pointless, but still is made. And it is more in support of the author than in attacking the claim.
(2) Cowardice. I watched things happen for years at ACM events. And I reported them each time, and finally decided to set up a video camcorder to offer ultimate proof. Jan Louman was the world's worst at interfering in a chess game by using the "move now" key to make the program he was operating move quickly when obvious, or to make it move before it changed to a worse move if a human IM/GM commentator had suggested that the current move being displayed is the obvious choice to win. Most did not want to discuss the topic when this was going on. Which was an indirect approval of the actions. If we are not going to discuss clones, and just stick to the "pablum" (baby cereal that is very bland for those not knowing the word) topics, then this place is not worth saving.
I've always been forthright about where _my_ code came from. It was originally 100% written by myself. Eugene wrote the egtb.cpp code and then let others use it as well,even though it was originally developed in Crafty by him. I am using Pradu's magic move generator idea, others used my rotated bitboard idea and some still do. But we are all quick to give credit to the source of the idea or code... Or "almost all". And many don't like to see proof offered that more was taken than should have been taken. We had this problem in many previous discussoins concerning Crafty clones. But suddenly discussing clones is not acceptable?
This is a crock. This is the major place where enough technically adept people are available to discuss this topic and reach a valid conclusion. And some want to suppress that entirely. Yes, accusing someone of creating a clone is a distasteful discussion. But if it isn't done here, and someone gets away with it, it is _far_ more distasteful, IMHO. And some want to suppress this. Until there is absolute proof. Which they _know_ is the old chicken and egg argument used to close off discussion to develop that kind of proof...
Vas could have taken several actions to avoid this entire mess (with respect to the Rybka discussion). He could have said "yes, I copied parts of Fruit code initially... I have since rewritten those parts and they are mostly gone..." He could have said "yes, I report a fictitious node count and depth value because I wanted to make it more difficult for others to figure out the new idea I have found and am using with great success. I knew that if I showed too much information, someone would discover my trick (this has happened for many programs over the years, dating back to Genius)." But he didn't, and the discussions have pretty well nailed him for doing exactly that. And some don't like it. But most of this has been purely self-inflicted.
Naum's status is unknown to me. If it is a clone, it will be discovered. If not, so much the better. But not allowing the discussion here really tends to render CCC as irrelevant. If that is the goal, you are getting there. If not, you need to re-think what is going on. I know that in the many terms I have served as a moderator, we _never_ cut off these kinds of discussions. This is a recent "bad idea". And I'll bet I have served as a moderator more than any other person here. Food for thought...
The "no libel" idea is a crock, and is just an excuse to avoid discussing a specific topic that nobody likes. Namely the Rybka came from Fruit discussion. I have my own thoughts which primarily leads me to conclude that there is way to much similarity to be purely based on random chance. I have looked at several open-source programs and never found duplicated piece/square table values as an example. But I'll admit that it is possible to come up with the same values independently, if you think flipping 1,000 heads in a row is something that won't take years at least. It is possible that two different programmers would use the same odd constructs. About the same again as 1,000 heads in a row. But both together? Now it is like 1,000,000 heads in a row.
Regardless of what is done in Rybka of today, R1 _clearly_ has significant parts of fruit included. That's old news. Those that want absolute proof know that such is impossible when anyone can write a 10 line program that will, given enough time, produce source code that is identical with fruit. The fact that this might take a few billion years to happen is not important to them. And given that, absolute proof is not possible. Fortunately, in most court systems, it is not necessary to have a video showing the crime being committed and with a clear facial image of the accused.
Trying to suppress such discussions is a sign of several problems:
(1) "author XXX" can't possibly have copied his program. It is stronger than what was supposedly copied. Argument is pointless, but still is made. And it is more in support of the author than in attacking the claim.
(2) Cowardice. I watched things happen for years at ACM events. And I reported them each time, and finally decided to set up a video camcorder to offer ultimate proof. Jan Louman was the world's worst at interfering in a chess game by using the "move now" key to make the program he was operating move quickly when obvious, or to make it move before it changed to a worse move if a human IM/GM commentator had suggested that the current move being displayed is the obvious choice to win. Most did not want to discuss the topic when this was going on. Which was an indirect approval of the actions. If we are not going to discuss clones, and just stick to the "pablum" (baby cereal that is very bland for those not knowing the word) topics, then this place is not worth saving.
I've always been forthright about where _my_ code came from. It was originally 100% written by myself. Eugene wrote the egtb.cpp code and then let others use it as well,even though it was originally developed in Crafty by him. I am using Pradu's magic move generator idea, others used my rotated bitboard idea and some still do. But we are all quick to give credit to the source of the idea or code... Or "almost all". And many don't like to see proof offered that more was taken than should have been taken. We had this problem in many previous discussoins concerning Crafty clones. But suddenly discussing clones is not acceptable?
This is a crock. This is the major place where enough technically adept people are available to discuss this topic and reach a valid conclusion. And some want to suppress that entirely. Yes, accusing someone of creating a clone is a distasteful discussion. But if it isn't done here, and someone gets away with it, it is _far_ more distasteful, IMHO. And some want to suppress this. Until there is absolute proof. Which they _know_ is the old chicken and egg argument used to close off discussion to develop that kind of proof...
Vas could have taken several actions to avoid this entire mess (with respect to the Rybka discussion). He could have said "yes, I copied parts of Fruit code initially... I have since rewritten those parts and they are mostly gone..." He could have said "yes, I report a fictitious node count and depth value because I wanted to make it more difficult for others to figure out the new idea I have found and am using with great success. I knew that if I showed too much information, someone would discover my trick (this has happened for many programs over the years, dating back to Genius)." But he didn't, and the discussions have pretty well nailed him for doing exactly that. And some don't like it. But most of this has been purely self-inflicted.
Naum's status is unknown to me. If it is a clone, it will be discovered. If not, so much the better. But not allowing the discussion here really tends to render CCC as irrelevant. If that is the goal, you are getting there. If not, you need to re-think what is going on. I know that in the many terms I have served as a moderator, we _never_ cut off these kinds of discussions. This is a recent "bad idea". And I'll bet I have served as a moderator more than any other person here. Food for thought...