[pron]

> Lately, they seems to work with CRIU, various heuristics, multi-stage in-process bytecode compilation ..

Not sure what you mean by this, as this has nothing to do with GC, and Java has had a multi-tier optimising compiler for 15 years now.

> that nobody else have, so fixes are available

Go has much worse problems with GC than Java does these days, and nobody else is able to achieve similar performance in large programs with heavy workloads. So everyone else lives with less sophisticated compilers and memory management simply by accepting worse performance.

[JackSlateur]

https://openjdk.org/projects/crac/ (based on CRIU: https://criu.org/Main_Page)

Your last phrase is probably is joke ? If not, please share reproductible numbers: some things per watt, some things per MB of memory.