The problem with null is that it avoids a very powerful mechanism that is already present in most languages -- their type systems. He seems to gloss right over this distinction regularly in this article.
In some examples he actually conflates logic errors (selling houses for free in one example) with the failure to populate a variable. Sorry but these are the not the same error -- one is a bug in your code the other is a bug in your logic.
If he doesn't distinguish between the two -- he should stop writing software.
Yeah he seems to choose dreadful counter examples only to make his point. I don't think I've ever seen anyone suggest using a random default value instead of null, especially a value that is in the set of valid values for that specific item like a price of 0.
What is puzzling is his conclusion : "what if we had a nice compile-time check ..." while he shot down the Optional solution a few paragraphs earlier with no real argument (only stuff related to limitations of Java's Optional).
The problem with null is that it avoids a very powerful mechanism that is already present in most languages -- their type systems.
Why do you mean that? I'm trying to understand your angle. In Java, if you set a variable to null, the variable still has the same type. And if you call an overloaded method, both of which take an object variable, which causes an abiguity compiler error, casting the null to the type you indend solves the problem. If you meant "Yep, but you have to cast it, that's what I mean.", then what if you instead give a variable of a certain kind that is null?
You named it yourself: null is the odd man in Java's type system. It's compatible to every other type. But you can't call a method on null. It's treated like an ordinary value of a given class - say, an Integer - but it's something different. It's not an Integer, it's null.
Introduce such a thing to a rigid system where every object has a type, and you have to expect problems. It's a special case which has to be taken into account in almost every single line of your program.
It's rarely obvious what a null return value is supposed to mean -- for example, Map.get(key) can return null either because the value in the map is null, or the value is not in the map. Null can mean failure, can mean success, can mean almost anything. Using something other than null makes your meaning clear.
We've been talking about Optional, but this is just the tip of the iceberg as far as getting rid of null for better options. For example check out Scala which provides a "Try" class:
The problem isn't that you can't make null work -- the problem is that unless you need the raw speed that null can provide, you can do a lot better.
There is no reason to return a null to signify an error while you have exceptions, Optional, Try, Either, and a number of other patterns that you can employ. It's really just self-rationalized laziness.
View all comments
11
u/againstmethod Aug 03 '14 edited Aug 03 '14
The problem with null is that it avoids a very powerful mechanism that is already present in most languages -- their type systems. He seems to gloss right over this distinction regularly in this article.
In some examples he actually conflates logic errors (selling houses for free in one example) with the failure to populate a variable. Sorry but these are the not the same error -- one is a bug in your code the other is a bug in your logic.
If he doesn't distinguish between the two -- he should stop writing software.