It is crazy that people still don't understand why JVM sucks, and why GO's approach to minimize GC pause latency is far superior design decision compared to whatever JVM has been trying to do with its GC iterations for god knows how many years with gazzillion different variants that all suck in different ways.
Go wins not by technical ingenuity, but by simply not making fundamentally bad decisions in the first place.
The very fact that Project Valhalla had to create new opt-in syntax for value classes, in order to get what Go does by default on all its types, is the admission of defeat of a herculean battle of attempting to optimize desite fundamental problems with Java's design.
Value classes won't make criticism outdated, because they don't fix any fundamental problems, they just provide an opt-in feature with significant restrictions.
If your argument is that optional syntax is bad, sure, we can do that, but it has nothing to do with GC performance.
Go's GC is nowhere near as complex, and yet it performs much better, because Go decided not to shoot itself in the foot.
Except this criticism will be outdated. (but then you moved the goal post to syntax).
> Go's GC is nowhere near as complex, and yet it performs much better
Benchmarks prove otherwise.
> Benchmarks prove otherwise
Well, good luck running the benchmarks on your production servers.
It should also be noted that the low pause Azul C4 collector was available in 2010, but it was a commercial product.
Design of Go allows programmer to rewrite their program to make it as GC efficient as needed. You can even have essentially zero GC overhead and do stuff manually for really high performance needs. And you can also write regular code when GC isn't a big deal.
Those options simply don't exist in Java language. Your only bet in Java would be to embed some C code which is a nightmare of its own.
There is a reason why almost all backened systems that run on JVM are a huge pain in the ass even at moderate scale. They all end up rewriting parts in other languages and at the end just rewriting the whole thing.