Yeah null safe types really renders optionals obso...

# announcements

[gjesse]

Yeah null safe types really renders optionals obsolete. Best I can suggest is an 'orNull' or unwrap extension function

[trevjones]

gjesse: I think that null safe types such as in kotlin exposes that optional was never an appropriate abstraction for dealing with null the way people wanted it to. Optional still makes sense when you are modeling domain concepts.

[gjesse]

I dunno, i find nullable as an indication of optionality to be way more intuitive. I still use optionals when writing Java though