Oracle's Java Policies Are Destroying the Community 314
snydeq writes "Neil McAllister sees Oracle's buggy Java SE 7 release as only the latest misstep in a mounting litany of bad behavior. 'Who was the first to alert the Java community? The Apache Foundation. Oh, the irony. This is the same Apache Foundation that resigned from the Java Community Process executive committee in protest after Oracle repeatedly refused to give it access to the Java Technology Compatibility Kit,' McAllister writes. 'It seems as if Oracle would like nothing better than to stomp Apache and its open source Java efforts clean out of existence.'"
Re:Watch me falling asleep over Javatalk (Score:5, Informative)
And LibreOffice is working on reimplementing many of those features without Java.
Re:Round 1. Fight. (Score:4, Informative)
They released version 3.4.2 three days ago [documentfoundation.org]. As I understand it they're mostly working on bug fixes for now--lord knows they need it--and removing as much Java dependence as possible.
Re:This is Oracle we are talking about.... (Score:4, Informative)
Apache did, in fact they reported the trouble five days before the deadline. This was a show stopper, Oracle did not treat it as such, Oracle has a habit of this. What they should have done (keeping in mind how they treat bugs) is released on schedule but with the option disabled. But no this would have been too much of a performance regression, again Oracle has made crazy decisions in the past where they value perceived performance in some benchmark above all other sane reasoning. But really they could have in this case, then around the second or third update have this fixed and it would have been another great release all about improved performance. That would look pretty dang good in comparison to the current situation. It is just that there is clearly some disease that has spread at Oracle, and they can't think things through clearly enough when there is a deadline or benchmark involved.
Re:Also in the news (Score:4, Informative)