I'm not sure if any of this is true and you seem to be contradicting yourself. Java is far less verbose than Go, and the compiler is leagues faster than kotlin's, graal's native compiler, probably most other languages, and I'm sure its faster than Babel. Javac doesn't do any optimizations, just emits bytecode. Why is it acceptable for Go to be verbose and kotlinc to be slow?
I'm not saying that Go or Kotlin is better than Java in all of those aspects. I'm just saying that Kotlin, GraalVM exists because Java, JVM have certain issues or limitation. For Golang, I'm just saying that the developer experience in Go is better. It's not just my personal experience, you can find the same result in any developer survey.
I clearly wasn’t surveyed. I don’t even like Java but I would need a an extender to my ten foot pole before touching Go. (Unless we are talking microcontroller embedded software, and I only could choose between Java and Go.)
I initially disliked Go as well, but it's a language that can only be truly appreciated when you start using it. Many of its advantages come from from its simplicity, explicitness, fast compilation speed, single executable binary, and some opinionated choices made by its authors. Unless you're working with a legacy system, Go (or Rust) is the preferred choice nowadays for distributed systems and system softwares (Kubernestes, TiDB, traefik, to name a few). It's also the default choice for numerous internet companies like Uber, ByteDance, and Monzo.
Here is a survey if you'd like to participate this year, but I don't think it will significantly alter the results.
I'm not sure if any of this is true and you seem to be contradicting yourself. Java is far less verbose than Go, and the compiler is leagues faster than kotlin's, graal's native compiler, probably most other languages, and I'm sure its faster than Babel. Javac doesn't do any optimizations, just emits bytecode. Why is it acceptable for Go to be verbose and kotlinc to be slow?