IMO JVM + Loom is the better runtime and with Kotlin it has the superior language also. Before Loom there was often a case to pick Go just for goroutines but t

IMO JVM + Loom is the better runtime and with Kotlin it has the superior language also. Before Loom there was often a case to pick Go just for goroutines but that time has passed for me at least. Go still has it's place in my toolbox, namely shuffling bytes from one fd to another when such a task is called for in an environment where the JVM would be too cumbersome or I just want redistributable binaries for one reason or another. (though Rust is increasingly consuming these use-cases for me I really don't like async Rust) The call out that Loom doesn't currently do forced preemption/time-slicing is notable though, for now you should make use of platform threads for CPU-heavy parallelism if you have tasks that simply won't yield. The fact you can still just use platform threads whenever you need them largely obviates that from being impactful.