null pointer exceptions shouldn't be possible in the first place

Swift, Kotlin and Rust were built on this idea.

Not nullable/optional, no unwrap.

And -1 should not represent an invalid index. If you don't always have a value, you shouldn't always return the type.

what's possible and what's happening is usually the difference between theory and practice

Hey guys, I just wanted to let you know that I recovered 6.26476 BTC I lost to a fake Forex Investment Company. Many thanks to hackrecovery AT yandex {DOT} ru, a professional recovery experts and team of hackers I hired to help me track and recover my funds. If there is any way you find Yourself in a similar situation, I will advise you to reach out to these guys. They are the best professionals in the market. I am so glad my funds were recovered through their support, this is one of the best decisions I made this year.

As someone who knows a big empty patter project. I highly disagree.

Having an application do random garbage instead of crashin isn't always great. Defining an empty atate isn't always easy.

Frankly, I really really don't mind them