DZone Research: Concerns With Java
DZone Research: Concerns With Java
The biggest concerns with the Java ecosystem are the deterioration of quality (with people not learning from their mistakes) and release fatigue from the new cadence..
Join the DZone community and get the full member experience.Join For Free
FlexNet Code Aware, a free scan tool for developers. Scan Java, NuGet, and NPM packages for open source security and open source license compliance issues.
To gather insights on the current and future state of the Java ecosystem, we talked to executives from 14 companies. We began by asking, "What’s your biggest concern with the current state of the Java ecosystem?" Here's what the respondents told us:
- Adding modules to Java 9 is a dead feature. Ultimately, Oracle will realize no one switched and stop supporting.
- Release fatigue.
- Competition from other JVM languages that are simpler. Competition with containers that provide build once run anywhere in a more integrated way.
- I don’t think that the Java ecosystem has taken security seriously enough. The applications that run the U.S. economy and many, many other critical apps are written in Java. It’s way too hard to build a secure Java EE application. It requires a massive amount of specialized knowledge and tricky code. Even preventing very well-known vulnerabilities, like SQL injection, XSS, XXE, CSRF, and OGNL injection are far too difficult. I think there’s an opportunity to cement Java as the go-to platform for the next decade if a serious effort were put into making Java security great.
- I don’t really have any. People dismiss Java, but I see plenty of opportunities. It still provides a large set of users, the best technology around, with strong features. We are actively trying to make Java smaller and more lightweight for microservices. We have built a VM with the same throughput at half the memory. We’re still innovating to make it smaller for dynamic scaling in the cloud, reconfiguration on the fly, and more Java SE platforms.
- As the language ages, at some point, it will no longer be an interesting career path for new engineers. When a new language starts to take over, the whole community of engineers will also start moving to that new, more exciting language and no one will want to work on the old languages. It’s really a people concern because if the pool of talent available to you starts to shrink, then the availability of quality engineers also shrinks.
- Adoption of Java 9 and 10. If they are not adopted there will not be sufficient feedback in the feedback loop. If they are integrated into open source projects developers are more likely to adopt.
- Now I worry that we are not attracting enough younger people into the Java programming career path. I think more youth would add to the vibrancy of our ecosystem. In general, I would like to see greater diversity, especially in the OSS portion of the Java ecosystem.
- Progress has been slow relative to .Net which has evolved more rapidly. Backward compatibility. Closures as a programming construct. Object-oriented versus future-oriented introduced in Java 8 still working to improve. Java 9 and 10 are too little too late.
- A big question for me at this time is how Oracle's role as a steward will look in the future. It's really good that they've opened up insights into Java with the OpenJDK and letting go of the JavaEE specs but what are their future plans for Java now that they are becoming a big cloud company?
Here’s who we spoke to:
Opinions expressed by DZone contributors are their own.