Earlier quoted context omitted.
> The JVM is a beast, why do you think a good deal of all serious web applications run on top of it? The JVM sacrifices latency for throughput, which is good for servers but not for desktops.
Look at ZGC GC. It has less latency due to stop-the-words than what the OS scheduler causes. (Of course at the price of throughput). But also the default GC, while on default being more throughput preferring can be tuned by a single paramater.
I did, it caused huge pauses with my application (I think probably a bug).
> But also the default GC, while on default being more throughput preferring can be tuned by a single paramater.
Sure, but how many people will do even that much tuning? Defaults are important, and IMO Java chooses a bad one; responsive by default and tuneable when you need maximum throughput is better than the reverse. (I suspect they picked the defaults they did to be competitive against C++ in benchmarks, but we're well past the time where that's what you're competing with).
Same as how Go and Electron have been very successful - not because they're great to work in per se, but because they have so much less friction between writing a hello world program and getting an executable you can distribute.