3 ms·

> They don't now but they likely will. See "named invocation" here: https://cr.openjdk.java.net/~briangoetz/a https://cr.openjdk.java.net/~briangoetz/a This is

> They don't now but they likely will. See "named invocation" here: https://cr.openjdk.java.net/~briangoetz/a https://cr.openjdk.java.net/~briangoetz/a This is good news! > It has little to no influence on the Java platform it targets and its ecosystem It certainly influenced the ecosystem by showing what is possible, and making the shortcomings of Java even more obvious. It has replaced Java (and to some degree, Scala) as the default backend language at some shops, because of less boilerplate and null-safety, leading to better and more maintainable code. Its running the apps on worlds biggest smartphone OS. It may not have pull over the JVM‘s direction, but afaik that had not been a problem so far. Kotlin‘s performance is on-par with Java.

pron 7y ago
> It certainly influenced the ecosystem by showing what is possible Not really. The new features are much similar to their ML (and Scala) counterparts, and ML was well-known to Java's original designers. It is simply a matter of priorities and familiarity. It is true that Kotlin made some ideas more familiar to the point that Java was able to adopt them, and that is why Java benefits from Kotlin existing as an option on the Java platform. The Java language tries not to adopt a feature until it has been tried for a long-enough time by a large-enough number of developers. > It has replaced Java (and to some degree, Scala) as the default backend language at some shops Yes, but to put it in perspective, its penetration on the Java platform is around 2-5%, not higher than Scala's penetration ten years ago. > leading to better and more maintainable code. That is a hypothesis that some believe but does not seem to have any actual empirical support. > Kotlin‘s performance is on-par with Java. Yes, and that is a big problem for Kotlin. Kotlin was created at a time of stagnation for Java -- Sun's last years and the first years at Oracle -- and when Android was still similar to Java. Those two platforms have now diverged greatly, and will diverge even more, and it will be impossible to have a language that is at once the same on those different platforms and aims not to introduce performance overheads. Kotlin will either split into two languages (like Java and Android's "Java"), focus on one platform, or introduce performance overheads.

pron 7y ago

> It certainly influenced the ecosystem by showing what is possible Not really. The new features are much similar to their ML (and Scala) counterparts, and ML was well-known to Java's original designers. It is simply a matter of priorities and familiarity. It is true that Kotlin made some ideas more familiar to the point that Java was able to adopt them, and that is why Java benefits from Kotlin existing as an option on the Java platform. The Java language tries not to adopt a feature until it has been tried for a long-enough time by a large-enough number of developers. > It has replaced Java (and to some degree, Scala) as the default backend language at some shops Yes, but to put it in perspective, its penetration on the Java platform is around 2-5%, not higher than Scala's penetration ten years ago. > leading to better and more maintainable code. That is a hypothesis that some believe but does not seem to have any actual empirical support. > Kotlin‘s performance is on-par with Java. Yes, and that is a big problem for Kotlin. Kotlin was created at a time of stagnation for Java -- Sun's last years and the first years at Oracle -- and when Android was still similar to Java. Those two platforms have now diverged greatly, and will diverge even more, and it will be impossible to have a language that is at once the same on those different platforms and aims not to introduce performance overheads. Kotlin will either split into two languages (like Java and Android's "Java"), focus on one platform, or introduce performance overheads.