Other than just wanting to be able to copy other people's work as they often do all the time anyway, I'm not sure I understand major tech giants' argument as to why APIs would not be copyrightable. They are, if anything, much harder to make well than their implementations.
-
Show this thread
-
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...
5 replies 0 retweets 16 likesShow this thread -
Replying to @cmuratori
The lawsuit is about the Java APIs. Any discussion of "the correct way to design something" is probably irrelevant. But I guess the point is that this is in line with engineering practice in other disciplines.
1 reply 0 retweets 0 likes -
Replying to @deguerre @cmuratori
Good building safety codes are hard to come up with but it'd be bad for everyone if you had to make your building less safe because someone claimed to own the code.
1 reply 0 retweets 0 likes -
Replying to @deguerre
But that is true of everything. Literally. There are no industries that wouldn't have more, cheaper existing things if you removed IP protection, whether it's safety or anything else.
2 replies 0 retweets 0 likes -
Replying to @cmuratori @deguerre
The question is, if you removed that protection, would you have gotten to the current place you are, or would nobody have bothered because there was no way to make a company in that space?
1 reply 0 retweets 0 likes -
Replying to @cmuratori @deguerre
_Especially_ with APIs, which today are absolutely terrible, I think it'd be a major mistake to declare ourselves done and to discourage people from investing in designing and perfecting new APIs. Which is exactly what removing copyright protection would do.
1 reply 0 retweets 0 likes -
Replying to @cmuratori @deguerre
Businesses will always have to weigh the benefits of making the API open or closed, and if they choose open, they get certain benefits, so they can decide whether to compete on design or implementation. That seems like a _good_ thing, not a bad one.
1 reply 0 retweets 0 likes
The market is always free to shun a closed API if it doesn't want the risks associated with that.
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.