In his post Project Jigsaw: Late for the train [1], Mark Reinhold [2]’s proposes "to defer Project Jigsaw to the next release, Java 9." He explains the reasoning for this: "some significant technical challenges remain" and there is "not enough time left for the broad evaluation, review, and feedback which such a profound change to the Platform demands." Reinhold also proposes "to aim explicitly for a regular two-year release cycle going forward."
Based on the comments on that post [3], it seems that this news is not being particularly well received by the Java developer community. Markus Karg [4] writes [3], "In fact it is a bit ridiculous that Jigsaw is stripped from JDK 8 as it was already stripped from JDK 7. ... Just give up the idea and use Maven." Jon Fisher writes [5], "I don't think this is a good idea for the java platform. ... Delaying this will only turn java in to a leagacy technology." The comment [6] from ninja [7] is, "Whatever route you guys decide to go, I think it's time to prioritize Java the platform ahead of Java the language."
Although this news is generally receiving unfavorable reviews from the Java developer community, the explanations do differ to some degree. Some of those commenting think the modularization of Project Jigsaw [8] is needed now (already may be too late), others [9] think OSGi [10] (or Maven or Ivy [11]) should be used instead and Project Jigsaw abandoned, others [12] would rather get other new features [13] and aren't worried about the modularization being pushed to Java 9, and others simply want to use Groovy [14] or Scala [15] instead. The question was posed [16] whether other features of Java 8 should be dropped in favor of Jigsaw.
As one of the two "flagship" features of Java 8 (lambda expressions [17] being the other one), I too am disappointed to see that it is likely that modularity will be delayed until Java 9. However, Reinhold points out that if the proposal to jettison Jigsaw from Java 8 is accepted, "Java 8 will ship on time, around September 2013" and is planned to "include the widely-anticipated Project Lambda [18] (JSR 335 [19]), the new Date/Time API (JSR 310 [20]), Type Annotations (JSR 308 [21]), and a selection of the smaller features [22] already in progress."
I really want [23] a new Date/Time API and I think the lambda expressions will dramatically improve [24] what we can do in Java. Because of this, I'll be excited to get my hands on Java 8 even without modularity.
Original posting available at http://marxsoftware.blogspot.com/ [25] (Inspired by Actual Events)
Links:
[1] http://mreinhold.org/blog/late-for-the-train
[2] http://mreinhold.org/blog/
[3] http://mreinhold.org/blog/late-for-the-train#comment-590312400
[4] http://www.java.net/blogs/mkarg/
[5] http://mreinhold.org/blog/late-for-the-train#comment-590314448
[6] http://mreinhold.org/blog/late-for-the-train#comment-590400995
[7] http://profile.yahoo.com/Z5DQCE7YHKZZWEDZIZLDYUUW5M
[8] http://openjdk.java.net/projects/jigsaw/
[9] http://mreinhold.org/blog/late-for-the-train#comment-590614057
[10] http://www.osgi.org/Main/HomePage
[11] http://mreinhold.org/blog/late-for-the-train#comment-590477900
[12] http://mreinhold.org/blog/late-for-the-train#comment-590456701
[13] http://mreinhold.org/blog/late-for-the-train#comment-590556003
[14] http://mreinhold.org/blog/late-for-the-train#comment-590442921
[15] http://mreinhold.org/blog/late-for-the-train#comment-590664800
[16] http://mreinhold.org/blog/late-for-the-train#comment-590429252
[17] http://earthly-powers.blogspot.com/2012/07/java-8-lambda-and-method-references.html
[18] http://openjdk.java.net/projects/lambda/
[19] http://jcp.org/en/jsr/detail?id=335
[20] http://jcp.org/en/jsr/detail?id=310
[21] http://jcp.org/en/jsr/detail?id=308
[22] http://openjdk.java.net/jeps/0
[23] http://marxsoftware.blogspot.com/2012/03/how-badly-do-we-want-new-java-datetime.html
[24] http://marxsoftware.blogspot.com/2011/10/javaone-2011-project-lambda-to.html
[25] http://marxsoftware.blogspot.com/