Null thread

Null is a mistake only if you're severely retarded

null is ok as long as checking for it is effortless and the fact that something might return null is either clearly documented or checked at compile-time (preferably both). if those conditions are not met, avoiding nulls wherever possible is a sane choice. with current popularity of fluent APIs (understandable: they make pipeline-like operations less painful), there's nothing worse than having to convert code like this:
hax()
.my()
.anus()

to this:
x = hax()
if x:
shit = x.my()
if shit:
FUCK = shit.anus()