&gt; there&#x27;s plenty of Scala and even some Clojure. But there&#x27;s also a move towards newer platforms like Node and Go. And there&#x27;s even been a rediscovery of platforms like Ruby and Python when the performance penalty doesn&#x27;t come into play.<p>I won&#x27;t say what you&#x27;re saying isn&#x27;t real, but it is happening on a completely different scale than the size of the Java ecosystem. Even on the JVM, what you see as &quot;plenty of Scala&quot; doesn&#x27;t even amount to 5% -- not that it matters, but it&#x27;s just an example of why I think your view is skewed.<p>The size of the Go ecosystem is hardly 1% of that of the JVM (rough estimate), and while Node.js&#x2F;Python are &quot;a thing&quot; (and are the only languages&#x2F;platforms of those you mentioned that are used to a substantial amount outside of startups), they are still tiny compared to the use of the JVM. Even in Silicon Valley (which is in itself a very small portion of the software world), the large &quot;webby&quot; application companies (with the notable exception of Facebook) are JVM shops: Amazon, Google, eBay, Twitter, Netflix are either entirely JVM or predominantly JVM, and even Facebook is making growing use of the Java.<p>Most of the shifts you&#x27;re seeing is among non-JVM technologies. It&#x27;s mostly Pythonists that switch to Go and Rubyists that switch to Elixir&#x2F;Node.js, etc.. The JVM was never the biggest player in the &quot;fast application development&quot; arena -- at the beginning there was VB, and then Perl, and then Python&#x2F;Ruby and so forth. I see no signs that there is greater movement away from the JVM -- mostly among those who realize they&#x27;re better served by the &quot;fast dev&quot; platforms even at the cost of performance -- than towards it -- by those realizing they need the best the industry can offer in terms of performance&#x2F;monitorability&#x2F;tooling even at the cost of slower development.