2 ms·
> For many years, Sun refused to provide the TCK to certify Apache Harmony as an official Java (donated to Apache by Sun's erstwhile foe, IBM[1]). Are you impl
by josefx 4y ago
> For many years, Sun refused to provide the TCK to certify Apache Harmony as an official Java (donated to Apache by Sun's erstwhile foe, IBM[1]).
Are you implying that GCJ was any more certified than Harmony? Because I would be surprised if it was, quite sure the TCK license was only opened up a bit when it became necessary to allow verification of OpenJDK derived implementations.
> had limited options for open-source Java compilers
As in none. They didn't have any options. So they fell back to GCJ, which could have been viable with significant time and effort. Instead it was still missing significant functionality even after OpenJDK was released, at which point it was too late.
I just realized how short the time between GCJ being able to run eclipse (2004) and being obsoleted by OpenJDK (2007) was, I somehow managed to set up enough new systems in that time frame to remember starting eclipse and realizing it was running on top of gcj as significant annoyance.
- sangnoir 4y ago> Are you implying that GCJ was any more certified than Harmony? No I am not. I am, however implying GCJ was as uncertified as Harmony, meaning they were seen as somewhat equals, despite Harmony's superiority (IMO). The situation would have been very different if Harmony had been officially blessed as Java, but I understand Sun's reluctance in cutting off its own revenue stream > As in none. GCJ and Harmony were the most well known Free/open source Java (the language) compilers, and were the choices available to distros that do not promote proprietary software. These, as you stated, were not Sun-certified Java™ due to the TCK situation - but they could compile java projects well enough.