View Single Post
Old 05-27-2016, 03:55 PM   #21
pdurrant
The Grand Mouse 高貴的老鼠
pdurrant ought to be getting tired of karma fortunes by now.pdurrant ought to be getting tired of karma fortunes by now.pdurrant ought to be getting tired of karma fortunes by now.pdurrant ought to be getting tired of karma fortunes by now.pdurrant ought to be getting tired of karma fortunes by now.pdurrant ought to be getting tired of karma fortunes by now.pdurrant ought to be getting tired of karma fortunes by now.pdurrant ought to be getting tired of karma fortunes by now.pdurrant ought to be getting tired of karma fortunes by now.pdurrant ought to be getting tired of karma fortunes by now.pdurrant ought to be getting tired of karma fortunes by now.
 
pdurrant's Avatar
 
Posts: 74,381
Karma: 318076944
Join Date: Jul 2007
Location: Norfolk, England
Device: Kindle Oasis
Quote:
Originally Posted by fjtorres View Post
Patent protection would be worse.

Copyrighted material can be legally reverse-engineered via clean-room code development. Patented material, it's not that easy; you can't replicate the same process with different code. Instead you have to achieve the same result via a different process. (Think: Type 1 vs TrueType.)
There's no way to clean-room reverse engineer an API. There is no code in an API. It's just a specification of the functions provided and the parameters to those functions. You use the API when you're doing clean-room reverse engineering. Allowing copyright over APIs prevents any kind of emulation of software.
pdurrant is offline   Reply With Quote