Earlier quoted context omitted.
There are serious fifteen year old reported errors in java.util.Random which have never been fixed and have finally been declared WONTFIX. Ten years ago I reported that ArrayList's get(), set(), and add() methods were non-inlineable (!) and could be trivially repaired with a single line of code: this was never fixed until recent versions of HotSpot which finally obviated the issue. We're talking core classes here. So…
The java classes have always had major warts and no one in charge has ever seemed to care . My personal bugbear: java.lang.Object depends on hundreds of classes including, among other absurdities, the Turkish locale (IIRC). This was about 13 years ago. Of course, the bug was eventually marked WONTFIX. 14 years ago, I adopted Java because it was a beautiful escape from the warty giant that C++ was becoming. Sun sat on…
The real story behind the Java 7 GA bugs affecting Apache Lucene / Solr
11–12 of 12 posts
Re: The real story behind the Java 7 GA bugs affecting Apache Lucene / Solr
#12Earlier quoted context omitted.
The java classes have always had major warts and no one in charge has ever seemed to care . My personal bugbear: java.lang.Object depends on hundreds of classes including, among other absurdities, the Turkish locale (IIRC). This was about 13 years ago. Of course, the bug was eventually marked WONTFIX. 14 years ago, I adopted Java because it was a beautiful escape from the warty giant that C++ was becoming. Sun sat on…
Could you elaborate?
- java issues / sun not caring - there are examples above by SeanLuke, gojomo and myself
- java.lang.Object depends on hundreds of classes - violates basic design principles of modularity and avoiding cyclic dependencies
- "Sun sat on it's laurels..." - apart from ignoring existing issues, they also ignored requests for language enhancements (e.g. dynamic language support, covariance, etc) for a long time causing many developers to give up on java for web development and move to python & ruby