4 ms·
> If you don't allow people to copy interfaces - where does that end? Does that mean that APIs should be protected from being copied? That is what I don't unde
by AnthonyMouse 11y ago
> If you don't allow people to copy interfaces - where does that end? Does that mean that APIs should be protected from being copied?
That is what I don't understand about people who argue that APIs should be copyrightable. It's like they don't see where the end is.
The reason competitors want to copy an API is because it's inherently necessary for compatibility. That need has nothing to do with how good the API is. It exists even if the API is terrible.
And APIs all chain together.
General Electric makes steam turbines. Your power company uses them to generate electricity. If GE (by analogy) controls the API then all power plants on the same grid have to use GE turbines. Your house connects to that grid, so you have to use a GE breaker panel in your house. It has its own API, so you also have to use all GE appliances.
If you want to charge your Macbook or iPhone at home then you had better hope that GE has a deal with Apple, and that they don't cancel it when GE enters the computing market. When they do you'll need a GE phone which will need a GE wireless carrier that will only serve GE websites. Now you can't buy anything from Amazon because you can't get there from here, you have to buy it from GE, and they only sell GE products. And so it goes.
Who are the people signing up for that world?
- rayiner 11y ago> The reason competitors want to copy an API is because it's inherently necessary for compatibility. That need has nothing to do with how good the API is. It exists even if the API is terrible. The other way to look at it is that people want to copy an API to extract value from a market or ecosystem someone else did the hard work of creating, without investing the resources into creating their own.
- AnthonyMouse 11y ago> The other way to look at it is that people want to copy an API to extract value from a market or ecosystem someone else did the hard work of creating, without investing the resources into creating their own. And why is that supposed to be a problem? You would prefer the world where Apple needs GE's permission to sell an iPhone that can charge from a GE power outlet? Ecosystems don't need owners.
- tptacek 11y agoThat depends a lot on our respective definitions of "ecosystem". You can expropriate a whole lot of value from all sorts of people by reframing part or all of their products as an "ecosystem" to which you're entitled access.
- AnthonyMouse 11y agoCan you provide some definition of "ecosystem" that would be problematic? I'm not proposing a law that says "you have a right to somebody else's ecosystem," I'm proposing that APIs not be copyrightable. You still have to provide your own implementation. I feel like I'm arguing against the position that you should have to service your car at the dealership because otherwise the independent mechanic who does the work is somehow illicitly expropriating value from the OEM. How is it that that has come to be a right of the OEM?
- rayiner 11y agoI think it's more like creating a car by reverse engineering Ford's in order to tap into Ford's ecosystem of parts and mechanics. Though I don't know where the line is. I think with API's: you can copyright the header, but not the ABI. I.e. nothing prevents you from making an LLVM module that exposes the same interface as what the header compiles down to.
- AnthonyMouse 11y ago> I think it's more like creating a car by reverse engineering Ford's in order to tap into Ford's ecosystem of parts and mechanics. So Ford makes the Mustang, I make after-market brake pads for the Mustang and therefore I have to use the same mounting interface as the Ford pads. I also make callipers and axles and so on; all the parts you need to repair your Mustang. In theory if I really make all the parts then I can put them together and get a whole car with no OEM parts. But notice that nobody really does this. Because if you're capable of making the whole car yourself, you no longer care if the parts are compatible with Ford parts, you just become Toyota. What you might see is people selling "whole cars" which are 75% Ford OEM parts and 25% something new and different, like the Shelby Mustang. But it's not clear how that should be something bad. > I think with API's: you can copyright the header, but not the ABI. I.e. nothing prevents you from making an LLVM module that exposes the same interface as what the header compiles down to. That's kind of weird. The header and the ABI aren't separable. You can decompile the ABI back into the header. Does it really make sense to be able to copyright something which is just a deterministic transformation of something you can't copyright?