Slashdot Mirror


Improving The Java Core Library

dautelle writes "Many Java developers are frustrated by the not-so-open process to improve/correct/augment the Java core libraries. Unless you work for Sun or belong to a JSR expert group, there is very little you can do to influence the future of the Java platform. Even the JCP route can be a frustrating one (e.g. JSR-108 withdrawn by Sun because not enough progress made in a timely manner). To address this serious issue, the charter of the Java Addition to Default Environment (JADE for short) has been extended, along with the release of JADE 7.0. Participation to the jade.* package development is truly open (unlike javax.*). The library already provides numerous useful classes, bug fixes, enhanced implementations of existing classes, etc. Hopefully in the near future, the library could become so useful that it becomes a de-facto complement to the JDK."

2 of 37 comments (clear)

  1. How times change... by crazy+blade · · Score: 5, Insightful

    Many Java developers are frustrated by the not-so-open process to improve/correct/augment the Java core libraries. Unless you work for Sun or belong to a JSR expert group, there is very little you can do to influence the future of the Java platform.

    What about MS? I think that they also wanted to "embrace and extend" Java as well at some point.

    My point is, that sometimes I feel like people think free software should always get its way as a matter of principle. The truth is, that you are free to write an alternative classpath. and distribute it with your own VM as it is. Quit moaning and join in with the guys at GNU Classpath. Sun doesn't mind. It's focusing on its own. That's what MS did.

    --
    To err is human, but to forgive is beyond the scope of the Operating System...
  2. And this is bad why? by SpootFinallyRegister · · Score: 5, Insightful
    Locking down the core libraries is a good thing.

    Yes, people could cram more and better functionality in there, and everyone is sure their idea will just make Java better; but every new version makes Java less and less portable. Adding the same functionality in a non-core library is every bit as effective, but doesn't add the additional requirement for a new version, and will avoid breaking and deprecating enormous existing bodies of code.

    If you need new or better/differently implemented functionality, you are free to add it. If Java is unable to accomodate the addition outside the standard library, then the platform has failed.

    Don't get me wrong -- I'm a fan of Java. But, if the core of a language needs to be constantly updated, its an unstable language, and bad for production development. I think Java can be stable, but it requires that the developers do just what they are. Keep the standard libraries standard, and not full of every shoehorned-in functionality they can think of. Its already bloated enough.