Slashdot Mirror


State of the OpenJDK Project and Java 7

LarsWestergren writes "David Flanagan, the author of Java in a Nutshell, has a nice writeup on the state of the open source development of the next version of Java. The article explains the difference between the JDK7 and the OpenJDK projects and how to join them. Furthermore, it has an overview of the release schedule, proposed language changes and projects of interest. A more technical and in-depth tracking of the language changes and proposed new features can be found at Alex Miller's blog. This is the first in a series, and 'each future installment will provide an update on what's currently happening in the latest builds from the project, along with a deep dive into a new feature or API that's tracking for inclusion in Java 7.'"

4 of 184 comments (clear)

  1. Waste of time? by thunderlizard · · Score: 2, Interesting

    Isn't the OpenJDK just a waste of time (or a reinvention of the wheel?). The Sun JDK is already open, with the source code available...

    1. Re:Waste of time? by Selivanow · · Score: 2, Interesting

      I for one want to see OpenJDK succeed. You see, I run Linux on a SPARC box. Guess What....I don't have any recent version of Java. There was Blackdown, but even that hasn't been updated in a while...license issues I believe.

      --
      -- ...trying to make digital files uncopyable is like trying to make water not wet. -Bruce Schneier
  2. Re:Swing Sucks by petermgreen · · Score: 2, Interesting

    ahh the horrible practice of hiding your applications startup time in the systems startup time. It is practices like that which make low end machines horrible to use and contribute to the feeling of bloat in a modern desktop OS.

    --
    note: i'm known as plugwash most places but i screwd up registering that here somehow in the past and now can't register
  3. Jesus, JDK7?! by Lysol · · Score: 2, Interesting

    Man, I've been programming Java since 1.x (yah, yah, I know). Is it me or does it just seem like the versions are getting a little whacky. I don't do much Java programming anymore, but it always seems like a jump in major number was a big issue if you have to maintain apps. Shit, how many people out there in the 'real' working world use 1.6? Prob no one. Last project I did (for a major bank) required 1.4.2 and it was deployed at the beginning of this year.

    I feel like it's great (again, even tho I'm not using it this year) that Sun is on top of stuff and 'looking ahead'. But I really wish they would do meaningful SMALL dot increments and quit shoving out a now major release every year or so. I know 1.5 was out a while ago. But why not keep making 1.5 REALLY super stable and optimized and make 1.6 ONLY the one with the new uber-Swing and whatever else.

    It's sorta like Microsoft coming out with Vista even tho no one want's to use it cuz all the 'new stuff' (which seems to have been cut at the last minute) isn't stable. Continuously having big releases makes people feel like they have to abandon the older releases so they can focus on re-learning all the new features that haven't made it out yet. I've seen this on teams I've worked with.

    I just think more stable, optimized, smaller point releases are the way to go. And Sun being an 'enterprise' company should know this.