3 ms·
Not copyrightable APIs is a fairly dangerous precedent. 1. Good APIs are hard. 2. Under Alsup's ruling, good luck competing with AWS sales org when they decid
by pacala 7y ago
Not copyrightable APIs is a fairly dangerous precedent.
1. Good APIs are hard.
2. Under Alsup's ruling, good luck competing with AWS sales org when they decide to offer your own APIs as a service.
3. Nothing prevents Google from inventing their own APIs, and licensing them under whatever terms they like.
As of Google vs. Oracle, it's pretty clear that Google appropriated Java to benefit from its penetration in the market place, instead of putting in the hard work to build their own. Apple has built their own ecosystem, ObjectiveC/Cocoa/Swift/SwiftUI. Microsoft has built their own ecosystem, C#/DotNet, or adopted and contributed to open standards, HTML5/Javascript/Typescript. Heck, even HP has built WebOS around open standards.
- orangecat 7y agogood luck competing with AWS sales org when they decide to offer your own APIs as a service If the only advantage you have over AWS is that developers would have to change the function names in their code, you're dead anyway. And copyrightable APIs mean that you can't offer an API compatible with AWS as a way to get developers to try your platform in the first place.