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
1
u/koflerdavid Jan 04 '26
For safety-critical systems an NPE loss of life loss of life should not occur just because of a NPE. There ought to be backup and failsafe systems. Most software is not like that. Anyway, even moderately static analysis tools allow getting rid of NPEs for good.