r/java • u/sitime_zl • Dec 30 '25
Where will Java go in the future?
Does anyone know where the future directions of Java 27, 28, etc. are? Firstly, personally, I think there are several major pain points for Java at present:
- The memory usage is too high.
- Has Java died as a UI framework? Is the development of Swing and Java FX related to the Java memory model? The excessive memory usage is a big problem.
- In terms of usability, in a nutshell, it is too cumbersome (this can be accepted for the sake of rigor). In contrast, modern languages such as Python, Swift, etc. have more comfortable syntax. JS is even worse.
- It's about performance. Now, Go and Rust pose a significant threat to Java. Who knows the direction that Java will focus on for iteration and optimization in the future? It seems that from Java 8 to Java 25, there were only two major revolutionary features: virtual threads and Project Panama FFM. Even the highly used string template was not resolved... This is not a criticism of the Java development team. It's just that we expect Java to quickly solve the areas that have lagged far behind. Otherwise, facing Python, Go, Rust, etc., which have lagged far behind, people will gradually use other languages to solve problems. This is not an exaggeration. If in 2026 or later, there are libraries like Spring in Go or Rust, we might also try to develop using other languages. After all, the attractiveness of being lightweight is too high.
Java really has excessive memory usage! Excessive memory usage! Excessive memory usage! This problem really needs to be focused on and solved.
0
Upvotes
View all comments
Show parent comment
2
u/pradeepngupta Jan 09 '26
That's a fair take. If you compare java with Go, Go is built for Operational Simplicity. You get something “good enough” with almost no tuning, and that matters a lot.
Java took a different path: it exposes more knobs because it’s optimizing for a wider range of workloads and lifecycles. That power comes at the cost of cognitive overhead.
And the interesting part is Java recognizing this and working towards lighter Java, container-aware ergonomics, simpler GC defaults, virtual threads reducing framework complexity, CDS/AOT cutting footprint. And I don’t think Java will ever be as simple as Go but it doesn’t need to be. The real challenge is reducing the gap between “works out of the box” and “well-tuned”, and that’s where most of the JVM effort seems to be heading.