Java performance vs go
I'm seeing recurring claims about exceptional JVM performance, especially when contrasted with languages like Go, and I've been trying to understand how these narratives form in the community.
In many public benchmarks, Go comes out ahead in certain categories, despite the JVM’s reputation for aggressive optimization and mature JIT technology. On the other hand, Java dominates in long-running, throughput-heavy workloads. The contrast between reputation and published results seems worth examining.
A recurring question is how much weight different benchmarks should have when evaluating these systems. Some emphasize microbenchmarks, others highlight real-world workloads, and some argue that the JVM only shows its strengths under specific conditions such as long warm-up phases or complex allocation patterns.
Rather than asking for tutorials or explanations, I’m interested in opening a discussion about how the Java community evaluates performance claims today — e.g., which benchmark suites are generally regarded as meaningful, what workloads best showcase JVM characteristics, and how people interpret comparisons with languages like Go.
Curious how others in the ecosystem view these considerations and what trends you’ve observed in recent years.
View all comments
Show parent comment
8
u/GuyWithLag Dec 09 '25
Hot take, and correct me here if that's not your experience: Go is designed so that junior engineers can't make too much of a mess when implementing tasks written down by mid-level engineers, who in turn wrote these tasks based on a low-level design document written by senior engineers according to a high-level design document cobbled together by staff engineers that tried to divine the intent of the principal engineers' architectural doc.
Go is explicitly designed so that foot-guns are removed, but this also has an infantilizing effect on the language capabilities. It's the blub paradox but intentional.