No one said they destroyed it. Google appropriated Oracle's intellectual property for Google's own use, specifically because Google didn't want to pay for the use of that intellectual property.
If I write a book and you read it, love it, and then retype the book, print it and sell it, you have violated my property rights.
You and many others here don't want it to be that way, but it is exactly that way.
This is a bad analogy. You don't need to copy title and chapter names to allow other people to "interoperate" (read, scan, and index I guess?) with the book. Moreover substantial creativity goes into title and chapter names. Both of which imply they should be substantially more copyrightable than APIs.
> This is a bad analogy. You don't need to copy title and chapter names to allow other people to "interoperate" (read, scan, and index I guess?) with the book.
Bad analogies are inevitable, and aren't the commenter's fault. It's the Federal Circuit's fault, for trying to blur the lines between functional matters (the domain of patents) and copyright matters. Any analogy that's simple enough to quickly understand will suffer from basically this same flaw, or else not apply to this case.
Oracle's trying to get copyright duration on the exclusive rights to something that falls under patent subject matter, so yeah, they're blurring the lines.
Ultimately, the problem for Oracle is that the APIs are too functional to be eligible for copyright protection, too abstract to be eligible for patent protection, and too generic to be eligible for trademark protection. But that doesn't stop them from trying to get the best features from all the above.
A better analogy (i think) is a city that has in its constitution "streets and building locations must be in the exact same spot and have the exact same purpose as they are in neighboring City B (eg a coffee shop must be on the corner of 2nd & 3rd, but which coffee shop it is doesn't matter as long as it does the same thing as the coffee shop in City B)".
Your analogy is false. Google didn't copy the whole thing; they copied the API. THat's analogous to copying the chapter titles but not the chapter contents, far more than it is analogous to copying the whole book.
No, it's more analogous, but worse so, IMO, to copying all the sentences of the book in a manner like this:
"Jack and Jill ran down the hill."
into
"Gil and Jacky descended the mound."
It's exactly the same story just with different implementations that exhibit the same behavior. They didn't make something compatible with Java -- they replaced Java with something exactly like Java.
It's even worse than the example above, because they kept the same names of the classes, interfaces, etc.
They had to keep the same names of classes, interfaces, etc. in order to copy the standard library’s API. And it’s not illegal to copy the titles of chapters and write your own story. Even if they’re very similar, if you do it properly (no peeking at original), there’s nothing illegal about it.
If I write a book and you read it, love it, and then retype the book, print it and sell it, you have violated my property rights.
You and many others here don't want it to be that way, but it is exactly that way.