days
-1
-2
hours
-2
0
minutes
0
-9
seconds
-1
-8
search
Poll results are in!

Developers are *still* using Java 8. What does this mean for Java 10 adoption?

Gabriela Motroc
Java 10

© Shutterstock /Castleski

We asked what Java version you’re currently using and we received almost 300 answers. Now it’s time to examine the results and see what this means for Java 10.

Earlier this month, we asked JAXenter readers what Java version(s) they are currently using. Almost 300 people participated in the poll so thank you all for your input!

Results show that most respondents are still using Java 8 (82 percent, to be more exact). Eight percent are using Java 9 and seven percent have not let go of Java 7.

This shouldn’t come as a shock, though. When Java 9 was released, we naturally expected that it would take some time getting used to it. Still — keep in mind that Georges Saab, chairperson of the OpenJDK governing board and vice president of development for the Java Platform group at Oracle said last July he expected “JDK 9 to be slower than 8 but on par with other major releases in the past.”

Six months ago, RebelLabs found that Java 8 was the leader of 2017’s language race, followed by Java 7 or older, Groovy, Scala, JavaScript and Kotlin.

More proof comes from Red Hat’s Mario Fusco:

According to our results from last year’s survey, Java 9 was the clear winner. This year’s preliminary results showed that 62 percent want to focus more on Java 9 in 2018 and only one in five respondents find Java 9 uninteresting. The upcoming versions (Java 10 & 11) will also play an important role for about one-third of the participants this year.

Speaking of Java 10, now that it’s here, one cannot help but wonder: have Java developers embraced Java 9 or are they still using older versions? Will they embrace Java 10?

Everything will be explained in the third part of our interview series in honor of the new release but why not share a sneak peek at our experts’ answers?

SEE ALSO: 109 new features in JDK 10

Will you be migrating to Java 10 anytime soon?

I’ve been using it for some time already. Test early, test often they say. And I believe that everybody should start using the beta versions as soon as they get released. Spotting difficulties and bugs is a community effort.

— Markus Eisele

I may migrate on some of my personal projects. I work as a consultant and most of my clients are large, conservative organizations that are very risk-averse, for that reason most of them will probably not migrate to Java 10 for some time.

— David Heffelfinger

As a Java influencer, I have obviously already experimented with the Java 10 early access version, and I will be migrating as soon as possible. But my clients just upgraded to Java 8, so Java 10 will have to wait a bit longer, unfortunately.

— Marcus Biel

The third part of the interview series (which includes the answers to the question mentioned above) will be published in early April. Stay tuned!

In the meantime, it seems that Java developers have already chosen their favorite Java 10 feature. Marcus Biel made a poll on Twitter to find out which features his followers prefer. As it turns out, people are really excited about Local-variable type inference (JEP 286), which enhances the Java language to extend type inference to declarations of local variables with initializers.

Our 11 Java experts feel the same — as Nicolai Parlog explains in one of this answers, “if widely adopted, it will change the way Java code looks even more profoundly than lambda expressions did.”

What’s your favorite feature?

Author
Gabriela Motroc
Gabriela Motroc is editor of JAXenter.com and JAX Magazine. Before working at Software & Support Media Group, she studied International Communication Management at the Hague University of Applied Sciences.

Leave a Reply

3 Comments on "Developers are *still* using Java 8. What does this mean for Java 10 adoption?"

avatar
400
  Subscribe  
Notify of
benneq
Guest

You asked the wrong question and now you came to a wrong conclusion.
You asked what the people are “currently using”. Not which version they want to use or which they prefer.

E.g.: We’re stuck with a Spring Boot 1.5 product which uses Java 8. It would take months to upgrade everything to make the compatible with Spring Boot 2.0. Though we can’t use Java 9 or 10.

Gabriela Motroc
Guest

You are right, thank you for noticing that.

Andrew
Guest

Benneq is right. We just migrated an application from Java 5 to 7, but too many components break with Java 8 and it will be years before there is a priority to upgrade the rest of the system. Many in the Enterprise space are constrained by time and budget to upgrade all their applications.