Suggesting that somehow figuring out the correct way to design something is less important than having filled in the functions with their (usually obvious) implementation is frankly rather absurd. If you want to argue _none_ of it is copyrightable, go ahead...
-
-
Show this thread
-
But arguing that somehow APIs are less important or less worth IP protection than other types of code dramatically undervalues how important systems design is relative to implementation. If forced to pick, I'd actually claim the opposite (APIs copyrighted, implementations not).
Show this thread -
This is because in my experience, the vast majority of my time as a programmer on a novel problem is spent figuring out how it should be broken down. Once I know that, the implementation is usually relatively simple.
Show this thread
End of conversation
New conversation -
-
-
what's an "api" anyway? should one be able to copyright a hash table? it certainly has an _interface_ that applications can _program_ against, making it an Application Programming Interface. should that be copyrightable?
-
lest you think i'm trolling or something - matters much more trivial than this have been given a serious consideration in court, i.e. see oracle v. google range check
End of conversation
New conversation -
-
-
Think patent trolls. How hard would it be to generate and patent APIs, without implementation?
-
_Patenting_ APIs would be terrible. But being able to copyright a complete piece of software, rather than only being able to copyright that piece of software _minus_ the API, doesn't make much sense to me at all.
- Show replies
New conversation -
-
-
How do you draw the line? Is something like a language's standard library interfaces copyrightable? If so, it makes it really hard to have independent implementations, which means it's not really a standard is it (at least not an open one.) Maybe the line is in "private" APIs?
-
Most of the concern around patenting of APIs is specifically in response to the Oracle v Google situation w.r.t Java. Supposedly these interfaces are public and open. So people ask, if that is copyrightable, does it mean one cannot write a strlen, memset or memcpy for C?
End of conversation
New conversation -
-
-
my opinion is that APIs shouldn't be copyrightable so that things like wine can be freely made
-
This. Imagine people starting to copyright web apis... /v1 No that one is taken, ah crap
- Show replies
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.