6 ms·
>> If APIs become copyrightable, what happens to any open source software the implements a proprietary API? That has implications for language implementations
by phkahler 6y ago
>> If APIs become copyrightable, what happens to any open source software the implements a proprietary API?
That has implications for language implementations too. Who would own the standard library for any given language? What about programs that call API functions? Are they derivative works too?
An API is necessarily functional first and foremost. It would cause chaos and some weird dystopian future if Oracle wins.
- pfortuny 6y agoIt is usually in the interest of the designer of the API to have as many users as possible. BUT in this case we are talking not of using part of an API (say the Math library to implement a physics engine is assembly and link it) but of reimplementing a whole language which has, as of today an when the events discussed took place (even if we agree to hate it) an owner.
- simonh 6y ago>It is usually in the interest of the designer of the API to have as many users as possible. When they first design and publish it yes, but Oracle didn't design and publish the Java APIs, they bought them after they had becomes very popular and widely used. At that point they don't need to care about making it popular, it already is, all they care about is milking that existing ecosystem for every penny they can get. If future API publishers care about this they can just license out their API spec, but right now Oracle just wants to be able to squeeze whoever they can until the pips squeak.
- pfortuny 6y agoI know, I know. But if the argument is abstract then we have to keep it so.
- dredmorbius 6y agoIn a market-consolidating world this argument rapidly loses persuasive power.
- tsimionescu 6y agoThe standard library is owned by the people creating it, and of course your work using the standard library is a derived work of that standard library. For example, glibc is owned by GNU, and it is licensed under the LGPL, so you are allowed to dynamically link it without having to release your own code under the GPL (or compatible). This is all happening today. The only projects that will be more seriously affected by this decision are WINE and similar - projects that are copying the API but not the implementation. Even here, it is very likely that WINE could win on Fair Use, since their copying is obviously done for interoperability. Also, APIs are obviously creative human works, and their purpose is first and foremost usability for the end-user.
- diminish 6y agoMaking a drop-in replacement for interoperability for any library or API could fall victim under the current law.
- joshuamorton 6y agoBut now if I write my own libc implementation, someone (who?) could come after me for violating their copyright on the libc api.
- tsimionescu 6y ago> who? That's an interesting question. Perhaps K&R? Or maybe their employer? Or perhaps by now the copyright may be with ANSI/ISO? But this does raise an interesting point, about who would own copyright on something that was not believed to be copyrightable for much of its history.
- josefx 6y ago> Who would own the standard library for any given language? Require copyright assignment or a guarantee for royalty free use by any implementation. Standards committees already have to deal with hidden patent dependencies someone might sneak in so this would just be another bullet point on paperwork that should already exist.
- R0b0t1 6y agoAnother interesting take: Machine architectures expose an API, and it may become impossible for anyone but a chip manufacturer to distribute a compiler.
- ColanR 6y agoThat sounds like a win for RISC.
- rocqua 6y agoMachine architectures are very much copyrightable right? That's why Intel license x86 to AMD. Thing is, for chip manufactures it makes no sense not to allow others to call this x86 API. Things could get dicier for other who try and virtualize a machine instruction set.
- garaetjjte 6y agoIsn't x86 licensing situation caused only by patents?
- bismuthsalt 6y agoARM has built a business around selling licenses for an instruction set, with multiple third parties implementing said instruction set in silicon.
- phkahler 6y agoARM uses patents to prevent other implementations, not copyright law.
- FartyMcFarter 6y agoI don't see the similarity. A compiler outputs machine code, it doesn't implement machine code. Google's Java implementation implements Java APIs.
- wtallis 6y ago