Java 7 Delays and Plan B

Mark Reinhold has posted a message about the planning of Java 7. In this message, he explains that the current schedule of the JDK 7 is completely unrealistic. This delay is due to the add of new projects (lambda, Coin, Jigsaw) and the acquisition of Sun by Oracle.

The current estimate by the team is that the JDK7 can be complete for a release around the middle of 2012.

But, Mark indicates a new option, the “Plan B”. With this plan, the JDK7 will be available at mid 2011 without Jigsaw and Lambda and with only a portion of the Coin Project. And JDK8 will be released in late 2012 with the complete set of features scheduled actually for JDK7.

Personnally, I think it’s a good idea to separate the two releases and have a first release soon. Like Mark says, it makes a very long time that we don’t have had a new Java release, so it will be interesting to have a light JDK7 before 2012.

And you, what do you think ?

Source : Re-thinking JDK7, by Mark Reinhold

 

  • Stefan Asseg

    I absolutely agree! Bring us a new Java release!

  • Stefan Asseg

    I absolutely agree! Bring us a new Java release!

  • http://www.jroller.com/dmdevito Dominique De Vito

    Yes, the plan B looks like a good idea, because the release of JDK 6 is “too old”, now.

  • http://www.jroller.com/dmdevito Dominique De Vito

    Yes, the plan B looks like a good idea, because the release of JDK 6 is “too old”, now.

  • http://monisiqbal.blogspot.com Monis Iqbal

    I think Plan A looks more solid. Two reasonse:
    1. Organizations will adopt a new release once in 2-3 years so its unlikely that they will first adopt Java 7 and then Java 8 just an year after it.
    2. If plan B is effective then there will certainly be intermediate delay when Java 7 is released and it could further delay the time of Java 8.

    On a side note, do check my video response to the issue: Behind the scenes of Re-thinking JDK7 (geek humor): http://monisiqbal.blogspot.com/2010/09/behind-scenes-of-re-thinking-jdk-7.html

    • Baptiste Wicht

      Nice video, thanks :)

      And effectively, you point 1 is possible. I don’t know how organization will do. But there is still a lot of organization who release code compatible with Java 5 (or even Java 1.4.2 :( ), so would it change something ?

      • http://monisiqbal.blogspot.com Monis Iqbal

        These organizations that you are talking about won’t bother much about the release date. I’m talking about my personal experience on an enterprise Java product. They evaluate a new major release of Java, frameworks being used, IDE and then after a year of their stability in the community they adopt them.
        I don’t know how many organizations operate this way but if they do then they would certainly prefer plan A or if it’s plan B then they would ignore Java 7 and adopt Java 8 directly.

  • http://monisiqbal.blogspot.com Monis Iqbal

    I think Plan A looks more solid. Two reasonse:
    1. Organizations will adopt a new release once in 2-3 years so its unlikely that they will first adopt Java 7 and then Java 8 just an year after it.
    2. If plan B is effective then there will certainly be intermediate delay when Java 7 is released and it could further delay the time of Java 8.

    On a side note, do check my video response to the issue: Behind the scenes of Re-thinking JDK7 (geek humor): http://monisiqbal.blogspot.com/2010/09/behind-scenes-of-re-thinking-jdk-7.html

    • Baptiste Wicht

      Nice video, thanks :)

      And effectively, you point 1 is possible. I don’t know how organization will do. But there is still a lot of organization who release code compatible with Java 5 (or even Java 1.4.2 :( ), so would it change something ?

      • http://monisiqbal.blogspot.com Monis Iqbal

        These organizations that you are talking about won’t bother much about the release date. I’m talking about my personal experience on an enterprise Java product. They evaluate a new major release of Java, frameworks being used, IDE and then after a year of their stability in the community they adopt them.
        I don’t know how many organizations operate this way but if they do then they would certainly prefer plan A or if it’s plan B then they would ignore Java 7 and adopt Java 8 directly.

  • http://www.jroller.com/dmdevito Dominique De Vito

    IMHO, Plan B looks like the best idea for everyone :
    - early adopters would be happy playing with a new release (JDK 7) within the next months.
    - other people would wait the following first “Service Pack” release (JDK 8) for adopting a new JDK, after JDK 6.

  • http://www.jroller.com/dmdevito Dominique De Vito

    IMHO, Plan B looks like the best idea for everyone :
    - early adopters would be happy playing with a new release (JDK 7) within the next months.
    - other people would wait the following first “Service Pack” release (JDK 8) for adopting a new JDK, after JDK 6.

  • javierbds

    I think retard does not mean what you think … I’d use delay.

    • Baptiste Wicht

      Effectively, you’re right :(

      Sorry. I’ll make the correction.

      Thank you

  • javierbds

    I think retard does not mean what you think … I’d use delay.

    • Baptiste Wicht

      Effectively, you’re right :(

      Sorry. I’ll make the correction.

      Thank you

  • http://www.moldremoval.net Mold testing service

    I think Plan A looks more solid. I absolutely agree! Thanks.

  • http://www.moldremoval.org/ Mold testing service

    JDK features help to us to do lots of work in computing.thanks for the sharing.

  • http://www.terrazzofloorpolishing.net/ Terrazzo Floor Polishing

    I absolutely agree! Bring us a new Java release! thanks .

  • http://www.terrazzofloorcleaning.net Restore Terrazzo Ft.Lauderdale

    Java 7 Delays and Plan B.

  • http://www.terrazzofloorcleaning.net Terrazzo Polish Ft.Lauderdale

    It will be interesting to have a light JDK7 before 2012.

  • http://www.terrazzorestoration.net Terrazzo Repairing

    So it will be interesting to have a light JDK7 before 2012.