@lupyuen The article doesn't really deliver any new insights. It's merely a statement of the obvious: That the state of null-safety in Java is a mess, and the Kotlin approach is really good.

I'd argue it's even better than stated, because despite what a lot of people claim, null is useful. And Kotlin is able to both keep null, and also make it impossible to accidentally get an NPE.