Bob,bob wrote:
And that is all nonsense, again. Similar algorithms does _not_ translate into similar code. I can't, for the life of me, imagine why anyone with any programming experience at all would keep raising this bogus point of view. It is simply nonsense. In my programming classes, I often wish it _was_ true, so that I would not have to look at so many different ways to do the same thing.
I think that Fabien is simply saying there are not many new original ideas in Fruit, no new algorithms. There is nothing in it which he could claim a patent for, I do not know the exact term. Fabien does not mention the GPL anywhere in this part of the interview that I can see, so I do not understand your description of nonsense.
A GPL violation would be a direct use of literal code from Fruit. As I understand it. A derivative work from Fruit, I think that is a broader specification, where Fabien states he only used commonly known algorithms. Would that not be up to some debate, when is there enough evidence a program is a derivative work from Fruit. Instead of a program making use of ideas found in Fruit. Comparing dis-assembly code, it should be possible to point to literal copies, but proving that something is a derivative work but not fair use of ideas, I think that is a bit harder.
Just the way I understand things, just as an interested reader. Is it much more complicated than that?
Thanks,
Eelco