That's not the point. The point is that any safety you think you have by using an Option is a little bit hand-wavy.
That's not _bad_, but the argument being made by the OP was that nullability in Kotlin was unsafe and inconsistent.
That's not _bad_, but the argument being made by the OP was that nullability in Kotlin was unsafe and inconsistent.
The problems arise when you interop with Java. At that point, shit can be null and you just don't know. My point is that it's the same problem in Scala as it is in Kotlin: Java interop adds a measure of unpredictability that needs to be handled at the touch points.