Over a million developers have joined DZone.

Anticipated Impact of Java 9

There's virtually no anticipation for Java 9 given the slow adoption of Java 8.

· Java Zone

What every Java engineer should know about microservices: Reactive Microservices Architecture.  Brought to you in partnership with Lightbend.

To gather insights on the state of the Java ecosystem today for DZone's Java Ecosystem research guide to be published in September, we spoke with 15 executives who are familiar with the Java ecosystem.

Here’s who we talked to:

Joel Depernet, E.V.P. Global Research and Development, Axway | Sacha Labourey, CEO and Founder, CloudBees | Rick Reich, CEO, Development Heroes | Asad Ali, Principal Software Developer and Lisa Hamaker, Marketing Manager, Dynatrace |  David Park, V.P. of Products, HackerRank |  Charles Kendrick, Founder and CTO, Isomorphic Software | Wayne Citrin, CTO, JNBridge | Raymond Augé, Senior Software Architect, Liferay | Laura Kassovic, Founder, MbientLab | Cameron Wilby, Co-Founder, Origin Code Academy | James Faulkner, Technology Evangelist, Red Hat | Paul Trowe, CEO, Replay Games  | Calvin French-Owen, CTO and Co-Founder, Segment

We asked our respondents, "What impact do you expect Java 9 to have?" Here's what they told us:

  •  Java 9 will take even longer for companies to adopt. Part of the success of Java has been its updates over time that seem to be at a better pace for the enterprise. It’s also a safe bet. .Net may create more energy in the Java Ecosystem. 
  • Jave 9 will be similar to 8 with enterprises slow to adopt. Anything that runs in the enterprise ecosystems are slow to adopt. There’s an underlying perception that Java 8 and 9 will lead to a more closed ecosystem.
  • Java 9 is modularity our stuff should work with 8 without modules and 9 with modules. 
  • I do not see Java 9 being as significant as Java 8. I have a little bit of fear and confusion over how the new modularity is being done. Is there misrepresentation of what will be possible? It’s not playing out as nicely as Oracle would like due to the lack of uptake. A lot of software is already doing modular. Doing all of this in a closed environment makes it difficult to close the gap. 
  • We won’t use Java 9 until we see uptake by our enterprise clients. We have a lot of clients who still haven’t made the transition to Java 8. 
  • Modularity with Jigsaw if it makes it in. However, we'll have to watch closely to see if it is ultimately included in Java 9.

What are your expectations on the impact of Java 9 or is it too early to tell?

Microservices for Java, explained. Revitalize your legacy systems (and your career) with Reactive Microservices Architecture, a free O'Reilly book. Brought to you in partnership with Lightbend.

Topics:
java 9 ,modularity ,java ecosystem

Opinions expressed by DZone contributors are their own.

The best of DZone straight to your inbox.

SEE AN EXAMPLE
Please provide a valid email address.

Thanks for subscribing!

Awesome! Check your inbox to verify your email so you can start receiving the latest in tech news and resources.
Subscribe

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}