I'm with you on that first one, but I fail to see how you can not claim compatibility. For instance, Apache Harmony is not Java(TM) and while it can not prove Java compatibility (obtain the TCK), it *can* claim it. Apache Harmony died not because it could not claim compatibility, but because it could not demonstrate it, thus nullifying its ability to be marketed as a drop-in replacement for the defined standard JSE. However, the claimed compatibility was fine enough for Google, who planned their own subset for Android relying only on a de-facto standard anyway (claimed but not proven).
Anyone can make an alternate implementation so long as they do not call it > Java and do not claim compatibility. > > Ralph. > -- You received this message because you are subscribed to the Google Groups "Java Posse" group. To view this discussion on the web visit https://groups.google.com/d/msg/javaposse/-/doqQd71_TQkJ. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/javaposse?hl=en.
