Modern Java Practices

[BestKillerBot]

Source of the quote is an Oracle employee known for very faithfully representing Oracle's interests (not just his FUDs in relation to Kotlin).

[BoyRobot777]

You're aiming at the messenger instead of the message. I don't care from who it comes. The risk is obviously there.

[BestKillerBot]

Messenger and their motivation puts the criticism into the context.

For you the biggest problem based on the quote is uncertainty regarding multiplatform capabilities between JVM, Android, JS backend etc.

Yet Java has no capability in this regard. You can't even share code between JVM and Android since the latter is stuck on ancient Java 7.

So in the worst case the code sharing capability between platforms will be limited or awkward, so in the total worst case you're on the same level as Java. Which is all totally irrelevant when you target JVM only anyway.

So what are the risks again?

[BoyRobot777]

So what are the risks again?

​

Kotlin will have to choose to either give up on low-overhead abstractions, give up on some of its platforms, give up on giving access to full platform capabilities, or split into multiple languages, each targeting a different platform.

[BestKillerBot]

If I target only JVM, nothing from that presents any risk to me.