Re: Of course, we all know why.
apparently not it the entirety. The other reasons:
Many programmers already knew the java API and it would and taken everyone of them lots of effort to learn the the Gobbledegoogle API.
Many programmers had existing java code that they could slot into new projects. It would have taken every one of them lots of time to re-write that code Gobbledegoogle.
If people had started writing code in Gobbledegoogle it would then need to be re-implemented in java if the same functionality was required in an existing java project.
Programmers used to understand the correct balance was that APIs were not protected but the implementation of an API were. This used to be the status quo as understood by the courts in AT&T vs the Regents of the University of California decades before Oracle and the appeal courts invented a new status quo because of java litigation.
Biting the hand that feeds IT
