

Scala calling Scala: you never use null, you never hit a problem with null.

> Kotlin's approach is superior in that it requires developers to deal with nullabilityīut it doesn't force them to deal with nullability when interacting with Java which is the only case where it matters. Why do you want an extra way of representing the same thing with more special cases? It's certainly not worth the cost of working with a weird, second-class type that you can't abstract over like other types).

(原始内容 存档于).Nullable types are worse than Option in every way that matters (yes they save a few bytes of memory occasionally, but who the hell cares, if you care about shaving 8 bytes off an object you won't be using the JVM in the first place. Today, at the Google I/O keynote, the Android team announced first-class support for Kotlin. ^ Kotlin 1.0 Released: Pragmatic Language for JVM and Android | Kotlin Blog.we expect Kotlin to drive the sales of IntelliJ IDEA The Advent of Kotlin: A Conversation with JetBrains' Andrey Breslav.

