Risks stifling innovative code?
http://groups.google.com/group/django-developers/browse_thre...
Eventually they wrote an adapter; I don't have any idea how they got the API spec, since they swore up and down they couldn't look at existing code.
(and, to be honest, the initial released version of their DB2 adapter showed some serious issues which may be related to not understanding how the code was supposed to work)
A better (more effective) one is, surely, dont reuse restricted code.... :)
I've synced code for my projects from sourceforge/google code/github often.
It is true we are not supposed to look at anyone else's source code though.
I realise the policy is probably not as originally worded here: but I was taking it somewhat literally to point out the fallacy of it.
At some point we have to trust devs to do their own work. This should show that no amount of policy can stop people ripping off work! Whatever the intention.
Reading code is always good; there is usually a net gain as long as it is ethical (i.e. not copied)
From what I know, people inside Microsoft make sure they don't get in to any legal trouble before they make use of any code or idea that's already available.
Anyways, this episode is a blatant disrespect for IP. Copying the code is something awful. I believe this case deserves the attention of authorities at Microsoft.