>> I still struggle with the fact that with the current API I still have to make my own object to Optional converter to handle nulls in what I think is a sane way. > > yes, Optional have not the same semantics as Optional (from Guava). Can you clarify this? Is this anything more than the lack of an Optional.ofNullable(T) factory?