Indeed, which why I am not terribly convinced by the argument that people might start throwing None around too carelessly if it becomes too easy to deal with None values. But perhaps I am biased here by the fact that I almost always write library code, so that there is an API barrier between me consuming maybe-None values and someone producing maybe-None values.