>You also would probably mention that the code would be less likely to be buggy and crash due to the null safety principle. Not really. Although it makes it easier to deal with null values, Kotlin is no miracle cure. A null value comes from somewhere. If your logic is wrong, your logic is wrong, no matter what is the language used.

I haven't used Kotlin extensively enough to know how much the null safety really helps, but this reasoning seems incorrect to me. You could extend it to say that static types aren't useful either, but in both cases there's a significant benefit from getting faster feedback that your logic is (or might be) wrong.