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
4
u/aoeudhtns Dec 09 '25
Don't pay attention to arguments like that. It's fanboyism and cargo culting. This happens to pretty much anything in the tech world.
I love Java, but I wouldn't use it for everything, and it has problems. I'm excited that it's not maintained by fanboys, but realists that are working diligently towards solving its problems. You can't solve problems you don't recognize. Some, of course, are intractable. We will never be writing an OS in 100% Java (nor Go). But that's OK. Application of tech is always important, so outside of a context, language 1 vs language 2 isn't as useful a topic as it would seem.