3 ms·
> APIs aren't designed in vacuum, they are the outcome of the work of a group of people that put in the effort and endless hours of work to design them. You co
by AnthonyMouse 7y ago
> APIs aren't designed in vacuum, they are the outcome of the work of a group of people that put in the effort and endless hours of work to design them.
You could say the same about the design of an electrical plug or a radio signaling protocol. That doesn't make the functional aspects of the design subject to copyright.
- pjmlp 7y agoBad examples, they are protected by certifications, market compliance processes, and paying for ISO and similar standard documents. Even implementators of languages considered free beer like C and C++, have at the end of the day have someone paying for those 100 CHF. Naturally there are black markets to work around those issues, then if a fire can be tracked back to a not-certified plug, the insurance can consider it isn't responsible for paying.
- AnthonyMouse 7y ago> Bad examples, they are protected by certifications, market compliance processes, and paying for ISO and similar standard documents. So then what do you need copyright for? Do the same thing for your API. Copyright is the wrong tool for this. But in particular, notice that if your "market compliance processes" start trying to charge monopoly rents, someone will reverse engineer the thing and launch a competing compliance process which insurance companies will happily accept as long as it has reasonable quality. Also notice that the compliance process for things like that is generally shepherded by a third party non-profit like UL or IEEE and not a competitor in the same market.
- pjmlp 7y agoThankfully some governments do believe in market regulations and certifications.