> So with this, the last thing Go had going for it over Java is gone, right?
No. Go does containerized microservices better because of its lower memory footprint. If you can use GraalVM then that might not matter.
No. Go does containerized microservices better because of its lower memory footprint. If you can use GraalVM then that might not matter.
Java stacks like Quarkus [1] have memory as low as 12MB and JVMs like OpenJ9 natively support CRIU for instant startup.
[2] https://blog.openj9.org/2022/10/14/openj9-criu-support-a-loo...
So no, it's not as simple and perfect in my opinion.
I regrettably don't remember the outcome though, and don't use either of them anymore to even test them readily, especially not under the same load.
And those Go binaries aren't runnable across a wide range of platforms like JVM apps are.
Likewise for "worse" ecosystem. It really depends on your context.
Edit: A closing thought: One thing I find enjoyable about working with Go is that it is tuned for my particular context. I also enjoy writing Java (and more specifically Kotlin) when that context changes (e.g. a desktop application).