Over a million developers have joined DZone.
{{announcement.body}}
{{announcement.title}}

The Future Of Java

DZone's Guide to

The Future Of Java

The future of Java is strong thanks to its ubiquity and stability. Check out what makes Java great and what Java 9 needs to do to continue the legacy.

· Java Zone
Free Resource

The single app analytics solutions to take your web and mobile apps to the next level.  Try today!  Brought to you in partnership with CA Technologies

To gather insights on the state of the Java ecosystem today, we spoke to nine executives who are familiar with the ecosystem.

We asked these experienced Java professionals, "What’s the future of Java from your perspective?" Here's what they told us:

  • I had moved away from Java and came back with Java 8. There’s a lot of innovation with Java 8 that we didn’t see from Java 2 through Java 7. Lambda is a game-changing feature and Java 9 is promising quite a bit with its modular system. The JVM is a robust platform that runs on all run times. The language may be superseded, but the JVM lives on.
  • It should remain stable and bulletproof. Software has become a short-term commodity. Java is a long-term guarantee that is consistently seen, and needed, by enterprises.
  • I’m just working with Java 8 at this point. There are plenty of opportunities. We’re exploring microservices with Spring Cloud and Spring Boot. Agencies are more comfortable with more stable versions of Java.
  • Java will remain robust and vital while maintaining a strong presence in the enterprise on the service side. Java is becoming more vital on the desktop since Java 9 provides an easy way to package apps. I think we’ll see more Java in the mobile environment. Oracle is pushing this. Traditional static-type languages will be the go to languages. The half-life of technology is getting shorter. It’s nice to know something is stable and will be around for the long-term so developers don’t become fatigued with all the changes.
  • Java 9 is the future as it tries to fix size and footprint issues. It’s ambitious. They didn’t understand the complexity, and they must get backward compatibility right. If not, it will hinder adoption. Spring and IntelliJ are doing early testing. I’m cautiously optimistic. We’ll see if it’s as successful as Java 8 with regards to tools, community, and frameworks. Get the footprint down for microservices and containers.
  • Java will continue to improve with solutions like Kotlin.
  • More movement towards microservices. Developers and clients prefer lightweight to heavy. That leads to faster development and deployment. Java must evolve more rapidly to support serverless programming with Lambda. If all application development goes to NodeJS, Java has a problem.
  • It will be around for a long time. It needs more dynamic ways to solve problems on mobile devices.
  • 1) It’s going to get faster. This is what Oracle is focused on. The open JDK is improving. 2) Security is a big, important factor. The innovation in Java 9 is great. The release cycle needs to speed up and be more reliable. Learn from what else happens in the JVM and add it back into the ecosystem. 3) More extensibility with more language implementations.

What's the future of Java from your perspective?

And in case you're wondering, here's who we talked to:

  • Kehinde Ogunde, Developer, Andela
  • Eric Shapiro, co-founder and Chief Executive Officer, ArcTouch
  • Prem Chandrasekaran, V.P. of Software Engineering, Barclaycard
  • Rajiv Kadayam, Senior Director of Technology Strategy, eGlobalTech
  • Anders Wallgren, CTO, Electric Cloud
  • Ray Augé, Senior Software Architect, Liferay
  • Wayne Citrin, CTO, JNBridge
  • Kunal Anand, CTO, Prevoty
  • Tim Jarrett, Director of Product Management, Veracode

CA App Experience Analytics, a whole new level of visibility. Learn more. Brought to you in partnership with CA Technologies.

Topics:
java ,java ecosystem ,jvm ,java 9

Opinions expressed by DZone contributors are their own.

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

{{ parent.tldr }}

{{ parent.urlSource.name }}