Java has just been on a roll with such substantial changes to fundamental pieces of the runtime! Great work to the teams that keep making improvements in backwards compatible manners.
This specific change seems to impact the JVM the runtime, not Java the language. Which is great for people like me, who heavily rely on JVM but couldn't care less about Java.
When some people (like me) say "Java", they mean the Java Platform, and they call what you call Java "the Java language". When you say JVM, I assume you mean the Java Platform minus the language (the language is ~3-5% JDK, the JVM is about 25%). People who use "the JVM" but not "Java" use ~97% of Java, i.e. the Java platform.
Funny, those languages rely heavily on the Java ecosystem and libraries, and they better hope the Java ecosystem keeps thriving, improving current libraries and producing new libraries else they become impractical. Show me your pure Clojure production grade http servers or database drivers ;)
This is what I hate in guest language communities (a subset of them), they literally spit in the ecosystem that makes their beloved language possible in first place.
Granted, not everyone is like that and there are many nice folks, but those vocal ones, oh boy.
>Show me your pure Clojure production grade database drivers
Depends what you mean by "database driver", but what disqualifies XTDB or Datomic, both of which have use outside of Clojure yet are implemented entirely in Clojure with the exception of the Java wrappers so you can use them naturally within Java or Kotlin?
Even then, talking about "pure Clojure" is a non-starter because Clojure is not a self-hosted language (yes, Java is self-hosted if you consider Jikes RVM, a JVM implementation in pure Java). Even if Java ecosystem were to dwindle, people can rely on the JavaScript, .NET, or Dart ecosystems thanks to ClojureScript, ClojureCLR, and ClojureDart existing.
I use ClojureScript daily and am not really affected by what happens in Java land. With that said, I always welcome improvements to the JVM, because I actually like the Java ecosystem; it's the only one that doesn't make me split hairs...despite the dreaded module system.
If you're referring to the storage engines, those are not Java, and even then, most storage engines of a database will resort to a lower level language because of the need to care about memory layout and things that are simply not exposed to you in a high-level language like Clojure (or Java, unless you are somehow able to use Jikes RVM in production, I guess, but I'm not aware of ANYONE using a Java storage engine atop Jikes)
