Yep, it's pretty interesting in light of Goslings previous comments on software patents and Sun's inability to make money or make good on its open source promises.
I feel for the guy, but if he didn't want to be slimed, they should have made the TCK available under an actual open source compatible license. If Google slimed Sun, what did Sun do to Harmony?
If the primary goal was compatibility, they should have worked with Apache on that. The license fees wouldn't have been a problem. If, on the other hand, the primary goal was controlling the single open source version of Java, you're going to have to expect non-"Java" open source forks.
I'm not sure what Google "sliming" Sun has to do with the copyright or the patent case, though. Is he suggesting that he agrees that APIs are copyrightable? (you wouldn't even need a TCK in that world)
I feel for the guy, but if he didn't want to be slimed, they should have made the TCK available under an actual open source compatible license. If Google slimed Sun, what did Sun do to Harmony?
If the primary goal was compatibility, they should have worked with Apache on that. The license fees wouldn't have been a problem. If, on the other hand, the primary goal was controlling the single open source version of Java, you're going to have to expect non-"Java" open source forks.
I'm not sure what Google "sliming" Sun has to do with the copyright or the patent case, though. Is he suggesting that he agrees that APIs are copyrightable? (you wouldn't even need a TCK in that world)