[sinsterizme]

This doesn’t refute his point, Java the language is separate from the JVM. And those big companies will follow the decreasing Java usage trend due to developer supply and demand. Anecdotally, it seems pretty obvious some of those companies are already doing this by writing new stuff in other, better languages when possible! To me that’s a good indicator a language is slowly dying, maybe you use a different definition.

[andyroid]

Pretty much any language running on the JVM will make it dead simple to import and use libraries written in Java - in fact one of the main reasons to choose the JVM is the huge amount of high quality libraries available. So while true that Java != JVM, it’s not as simple as that either.

[pjmlp]

Most JVM implementations are around 80% Java with some C++ for the JIT/AOT and GC, GraalVM and JikesRVM have even bigger percentage.

It is an illusion to use JVM without touching or understanding Java works.

[andykx]

I mean, I know tons of Scala and Clojure devs who don’t touch Java at all in their day to day work. I don’t think the user(s) above were referring to the implementation of the JVM.

[pjmlp]

Then something blows on their face and they are completely lost, because they don't know what powers their code or the boilerplate magic that they generate to pretend to be Java for the JVM.

I have seen a couple of those guys, where I get called to sort out their problems.

[afiori]

But this is still compatible with Java slowly dying. It is possible that in a future Java role in the JVM will share some similarities with C's role in CPython.