I think the strongest use case for this library is
s = readSomething();
if (!s.isNullOrEmpty()) { use(s); }
where otherwise you _never_ do anything with s again at all.
In that case, I can agree the library is harmless... but still, what's wrong with `s == null || s.isEmpty()`?