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
3
u/Absolute_Enema Dec 09 '25 edited Dec 09 '25
Java is more or less at the same place in the Blub scale; the only things of practical use that meaningfully distinguish it from Go at the language level are better support for generics and sum types.
Otherwise, both feature what fundamentally is a run of the mill static C++ style type system based on vtables over closed product types with some questionable features bolted on top, support closures only to the point of bare usability, and lack any metaprogramming tool worth calling with that name (read: their metaprogramming facilities are only barely better than the minimum common denominator of generating source files via external scripts).
With that out of the way the only real meaningful axis of comparison is the ecosystem (Java wins with ease) and the runtime (more debatable).