3 ms·

Java's GC has better throughput, because Go's GC specifically optimises for latency. This may or may not be the right tradeoff for you specifically, but it is a

by pdpi 4y ago

Java's GC has better throughput, because Go's GC specifically optimises for latency. This may or may not be the right tradeoff for you specifically, but it is a perfectly reasonable tradeoff. Jars are more portable at the cost of requiring a JVM installed on the target, whereas Go's statically linked binaries and great cross-compilation make portability mostly moot for server applications. Also, with Java 21, the JVM brings runtime support for virtual threads, at the VM and standard library level, but there is no real language support, whereas Go has actual support with syntactic sugar around goroutines, channels, and select statements. Tooling and the sheer number of libraries are definitely Java's biggest draws, but it's not enough to justify choosing Java over Go across the board.

killerstorm 4y ago
JVM has many different GC implementations, some of them are optimized for low latency, and, in fact, come with guarantees.
kaba0 4y ago
Java also has a low-lat GC which is also better than Go’s at the relevant metrics (ZGC).
lenkite 4y ago
If you wish statically linked binaries and cross-compilation, you can use GraalVM https://www.graalvm.org/22.0/reference-manual/native-image/StaticImages/ https://www.graalvm.org/22.0/reference-manual/native-image/S.... Fully accept that Go has the superior cross-compilation story, though you can do this via Github actions if you really want this for Java. https://github.com/marketplace/actions/github-action-for-graalvm#building-a-helloworld-with-graalvm-native-image-on-different-platforms https://github.com/marketplace/actions/github-action-for-gra... As for GC - Java is superior in nearly all respects. But you are right that common programming libs+paradigms in Java produce too much garbage. This has changed with lean and memory-sensitive frameworks in Java nowadays - like Quarkus https://quarkus.io/ https://quarkus.io/

by pdpi 4y ago

killerstorm 4y ago

JVM has many different GC implementations, some of them are optimized for low latency, and, in fact, come with guarantees.

kaba0 4y ago

Java also has a low-lat GC which is also better than Go’s at the relevant metrics (ZGC).

lenkite 4y ago

If you wish statically linked binaries and cross-compilation, you can use GraalVM https://www.graalvm.org/22.0/reference-manual/native-image/StaticImages/ https://www.graalvm.org/22.0/reference-manual/native-image/S.... Fully accept that Go has the superior cross-compilation story, though you can do this via Github actions if you really want this for Java. https://github.com/marketplace/actions/github-action-for-graalvm#building-a-helloworld-with-graalvm-native-image-on-different-platforms https://github.com/marketplace/actions/github-action-for-gra... As for GC - Java is superior in nearly all respects. But you are right that common programming libs+paradigms in Java produce too much garbage. This has changed with lean and memory-sensitive frameworks in Java nowadays - like Quarkus https://quarkus.io/ https://quarkus.io/