<https://www.forbes.com/sites/oracle/2019/07/01/ve...
# feed
n
did he really call kotli na cute baby that has to grow up ?
a
Well, Java is good and going in the right direction. The problem is you need to live really long to see the right things happen.
🧌 1
☝️ 12
p
Keep in mind that Venkat is a big fan of Kotlin 🙂
👆 2
👍 4
t
why this is funny
j
i wonder how they would implement null-safety without breaking the language
probably annotations, @NotNullable or something else that's verbose
p
i wonder how they would implement null-safety without breaking the language
The same way the Kotlin did 😉
j
Java would have to do it the other way around, String would have to be nullable and @String or String? would have to be non-nullable
Unless they introduce a breaking change which they probably won't do
p
Well, in Java you’d need to go the other way around since current type system assumes that everything is nullable
But other than that, no biggie - just like with Kotlin
Another issue is if it makes sense to introduce something like that to an established language and commit to maintaining it potentially forever
j
they could probably just continue to treat String like String! and then introduce ? for nullable and some other symbol for non-nullable. Would be weird working on a mixed Kotlin-Java project where the meaning of String? is swopped between Java and Kotlin
v
No offense but I think this is pure marketing stunt pulled off by Oracle. Oracle knows that it has been lagging on Java and with new JDK release cycle/policy the F**KED UP! Google is now pushing behind Kotlin and I don't see a reason why Kotlin won't give a strong competition to Java proving "baby" that has evolved already.
p
If you want to avoid completely null, you can use Optional.
Actually, Java will never be a mobile language again!
j
yeah, especially not after that Oracle lawsuit against Google
👆 3