1) the JVM itself is extremely battle tested now. There are even viable alternative JVMs. In terms of troubleshooting, reliability and management, the JVM is a non-issue. It's like the sun rising in the morning.
2) The knowledge base of solved problems, libraries, projects and skills for the JVM world dwarfs
3) Interestingly, the world of Java.next languages such as Groovy, Scala, Clojure is really getting traction. This is closely tied to #2, the smartest people in the world work in the JVM space. Clojure in particular is very nice, and you can deploy Clojure apps as Java jars, so in a stodgy big company setting, you can actually deliver.
4) Finally, a problem I've seen since with Microsoft over the years (still a problem) is that MS solutions tend to address a problem facing *Microsoft the company* but do not address problems facing *developers and customers*. MS is reactive. When Java began to shake up the scene, MS rushed to market with a "me too" version (the
The primary function of the design engineer is to make things difficult for the fabricator and impossible for the serviceman.