> Also, I'm skeptical on the "increase costs" claim. The reason Java "worked" at the turn of the century was because corporations would gladly reduce developer

> Also, I'm skeptical on the "increase costs" claim. The reason Java "worked" at the turn of the century was because corporations would gladly reduce developer time for the tradeoff of spending more on hardware if they needed performance. That's sounds great until you have to pay the cloud bills roll in. At the turn of the century options were limited. Now they're not, and that's the world Java has to compete in today. Java is slowing giving up ground as a result. An idiomatic Golang program, for instance, uses far less memory to perform the same tasks as the equivalent Java.