News for hackers. Stuff that matters.
Re:Java 24 by pjmlp on Tuesday March 18, 2025 @11:18AM (#43400483)
It is the Java Virtual Machine, not Kotlin Virtual Machine.

Thus Kotlin will always be a guest language and not the target of all companies designing JVM implementations.

That is left for Google with their .NET flavour, ART + Kotlin, where Android Java plays the same role as J# did for .NET, after Microsoft had let go of J++.

Re:Java 24 by msgilligan on Tuesday March 18, 2025 @01:14PM (#43401947)
> Thus Kotlin will always be a guest language

If you a writing libraries for the JVM, Java is preferred to Kotlin because it does not drag along a standard library dependency.

To be fair there is Kotlin Multiplatform where this is not the case. https://kotlinlang.org/docs/multiplatform.html

Re:Java 24 by pjmlp on Tuesday March 18, 2025 @01:58PM (#43402549)
Yes, and it has the issue of having its own way of #ifdef, because not all platforms offer the same semantics.

It is no different than writing C code across UNIX, Windows, mainframe, microcomputers and embedded, consoles, and somehow work across all of them.

Re:Java 24 by samus on Wednesday March 19, 2025 @06:33AM (#43410224)
Android Java is almost identical to mainline Java nowadays.
Re:Java 24 by pjmlp on Wednesday March 19, 2025 @09:23AM (#43411619)
Android Java is stuck in a subset of Java 17 LTS, released in 2021, hardly almost identical to mainline.

And this only happened, most likely because the Android team realised Kotlin was losing access to modern Java libraries, with ART being stuck in Java 8, so there was an update cycle for Java 11, followed by one for Java 17.

So far there are no public plans to update ART for something newer in Android 16, from the previews made available thus far, they actually also started rewriting OS components into Kotlin, it is no longer only Jetpack libraries.