Personally I find ?.let et al to be terrible for readability; most of the time you're better off doing a standard != null check. The same with nullable extensi

Personally I find ?.let et al to be terrible for readability; most of the time you're better off doing a standard != null check. The same with nullable extension functions; they hurt readability. > Null is a valid state, not something incredibly scary best dealt with with a full reboot or better yet throwing away the container. Kotlin is about making peace with null, instead of pretending that null does not exist. (yes, I'm looking at you, Scala) I honestly find this to be such a weird thing to say or imply. No one is "scared" of null.