It creates an interesting problem, as sometimes you want to know the absence of value. Usually done with the empty "" string.
The other way to handle is that every Object is initiated (pointing) to an starter initial value. (prototype based languages).
Sometimes you do want to represent the concept of “this whole datatype OR nothing”. How do you suggest this is modelled? I think optionality is pretty fundamental. What’s wrong about classical null is that it ascribes optionality to all types regardless of whether they need it.
Being forced to represent optionality with a “special” default is terrible design IMO - see the recent SSH RCE on Musl, largely due to the poor choice of indicating “crypt failed”. Default values can be quite dangerous. Sometimes the domain you are modelling supports such a value, but having “default value” be the default (and not a choice) is a similar evil to default null.
2. Use null coalescing (e.g. `foo?.bar?.baz`)
Languages such as Kotlin and C# support this style o programming.
The thing that I don't like about Optional types (in e.g. Scala or Java) is that they are too verbose. For example, instead of:
return foo?.bar?.baz ?? 0
you have something like: return foo.flatMap(_.bar).flatMap(_.baz).getOrElse(0);
This is even harder to read if you have more complicated logic, requiring implicit lambdas and other machinery.Initial values, like null, is an attempt to smuggle the "unset" case into the type without declaring it. And like null, the defensively written logic should prefix every single usage with a check for validity.
Optional is just a natural subset of the generalization that multiple possible states exist; in this case, just the two, and sum types to properly handle bigger sets.
Initial/null never admit more than 2 possible states, and also believe everything is always in one of those 2 states.
fwiw john carmack agrees with me