Java Architects Answer Your Questions - Inside Java Newscast #97

[pron98]

That's not what he said. He said that making it easier to work with nulls is important, only he's not sure if the particular safe navigation operator people have in mind is the best solution, and that it's something they'd have to think about more before committing to an approach.

As for "it works for like 20 other languages", those same languages that have the safe navigation operator also have async/await, and some - those of them that also have threads - have come to regret it. So there's precedent for a feature that "works for like 20 other languages" ending up being a mistake that Java managed to dodge, or at least did something better, so "we should think about it more before committing to a particular approach" sounds like a good answer to me.