This article is like a fiction the "Java Land". To the Java language designers, it would be like a space-age concept.
Lisp being mostly a class of dynamically-typed languages, their solution to the issue doesn't really apply to Java. For statically typed languages, the solution adopted by the ML family (as well as haskell) is far superior: encode the notion of "optional" values in an abstract type.