It seems to me that the IsNullOrEmpty problem could be solved by changing String.Equals() to throw an ArgumentNullException if the argument passed is null. This would solve Miguel's complaint that Jesse's proposed solution masks bugs, but allows Jesse to write String.Empty.Equals(x) without checking x == null first.