Java 7 Polls: Ultimate Impact (Results), and When You'll Use It (Just Started)
Leading up to the Java 7 launch (end of this month), java.net has been running Java 7 related polls. The first poll, which ended this past Friday, asked What impact will Java 7 ultimately have on Java's future? The poll drew 84 votes and 6 comments. Here are the results:
What impact will Java 7 ultimately have on Java's future?
- 7% (6 votes) - It makes Java the clear first choice among mainstream languages
- 40% (34 votes) - Java will continue as a leading language
- 31% (26 votes) - It keeps Java viable for now, but Java 8 is really needed
- 11% (9 votes) - No impact: Java 7 is too little, too late
- 10% (8 votes) - I don't know
- 1% (1 votes) - Other
Considering programming languages in general, almost all of them expand with respect to new features early in their course of development. A question is: is continued expansion of a language always required? To more than a few, Java had become "bloated" by the time we reached Java 5.
Some languages basically stop changing at some point, yet remain widely used, due to their suitability for specific roles and applications. Languages like C and Fortran come to mind.
With Java, it seems like few would consider it a satisfactory situation if the language just became fixed in a certain state -- especially not the end-of-Sun state. Historically, there has always been momentum for new enhancements to Java. In the case of Java EE, the recent momentum was in multiple directions: a capability for much greater simplicity (i.e., "bloat" elimination, thereby facilitating -- or, re-facilitating? -- the development of fast, lightweight, highly scalable Java EE components); there was also momentum toward tunability (through the new profiles capability), with the result that Java EE can be more compactly applied to address differing engineering needs. So, with Java EE 6, Java EE expanded, yet it "shrinks" as it is applied to specific objectives.
So, looking again at this (unscientific) poll's results: what's the consensus? I'd say most people who voted think Java must continue developing, moving forward; that Java 7 is a good step in the right direction; that Java 8 is a bigger step in the right direction.
The comments included some well-expressed contrary views. For example,
jwenting considers Java 7 a:
massive list of me2! features trying to turn Java into Ruby#++ aren't going to do anything to increase Java's massive market share. If anything, it will hurt the status of Java in the professional market... For serious development work, 1.5 was the end of the line. A 1.6 JVM running 1.5 code can give a bit more performance and stability on 64 bit systems, but that's about it. The only reason most professional teams moved away from 1.4 was that it went end of life, but most still code to 1.4 standards...
xylifyxcited the fact that:
We still don't have a expected release date for the mac version of Java 7 or JavaFX, until then Java 7 is not write once run everywhere. Write once run everywhere is probably Javas main advantage over competitors.
New (current) poll: when you'll use Java 7
Our current java.net poll asks "When do you expect Java 7 enhancements to become part of your code base?" Voting will be open until Friday, August 5.
- Malcolm Davis, Sexappeal, the space shuttle, and end of an era ; and
- Markus Karg, JAX-RS 2.0: A first interim report.
Our latest java.net article is Nadine McKenzie's Streamline JSF Development with These 3 Facelets Must-Knows.
Here are the stories we've recently featured in our Java news section:
- Peter Pilgrim invites you to Meet Your JavaOne 2011 Rich Media Track Reviewer;
- Stephen Colebourne, considering Kotlin, talks about Reversed type declarations;
- Geertjan Wielenga talks about an interesting Desktop Effect on the NetBeans Platform;
- Shai Almog writes about Toggle Buttons & Grouping Them Together;
- Just published - Java Spotlight Episode 39: Daniel Smith on Project Lambda;
- Stephen Colebourne talks about Kotlin and the search for a better Java;
- James Weaver has a new article on the OTN, Using Transitions for Animation in Oracle's JavaFX 2.0;
- Markus Eisele has suddenly realized that JavaOne is looming on the horizon - 6,393,600 seconds to go!; and
- Byron Nevins answers the question How Does GlassFish Pick the JVM to Run In?.
Our latest java.net href="http://www.java.net/archive/spotlight">Spotlight is the announcement New Java 7 Summit To Be Held at EclipseCon Europe:
The Eclipse Foundation, in collaboration with Oracle, is pleased to announce the Java 7 Summit, to be held at the upcoming EclipseCon Europe in Ludwigsburg, Germany on November 2-4, 2011. The Java 7 Summit offers Java developers and architects an opportunity to gain in-depth technical education on the new innovations...
Our previous Spotlight was Alexis Moussine-Pouchkine's Aquarium post JavaOne 2011 Content revealed & Duke Choice Awards Nominations!:
The JavaOne 2011 event catalog is now available with keynotes, sessions, hands-on-labs, BOFs, panels and user-group meetings is now available. While the schedule is not quite ready yet, this should give you a detailed view at this year's content which we hope is rated as good as last year's...
Subscriptions and Archives: You can subscribe to this blog using the java.net Editor's Blog Feed. You can also subscribe to the Java Today RSS feed and the java.net blogs feed. You can find historical archives of what has appeared the front page of java.net in the java.net home page archive.