3 ms·
>more and more information becomes encoded in the declarations I don't see how this is true at all. We've moved continually toward higher-level APIs. There's a
by dpark 10y ago
>more and more information becomes encoded in the declarations
I don't see how this is true at all. We've moved continually toward higher-level APIs. There's a lot more "magic" in String.split than strtok.
If your API is so specific that the implementation is entirely implied by the declaration, then all that means is that the implementation itself is trivial, in which case I don't think your API implementation should copyrightable either.
- cmdkeen 10y agoBut it isn't a single function definition it is the whole API. Deciding that you want to pitch your API at a specific level of abstraction and ensuring that level is consistently maintained across a whole language is hard work. The recent criticisms of ASP.Net Core's API changes or PHP's "interesting" APIs over the years surely demonstrate that writing language APIs is hard.
- dpark 10y agoSure. Coming up with a good recipe is also hard, but recipes are not copyrightable. Difficult does not always imply copyrightable.