string.Empty

[Jon Skeet [C# MVP]]

Sure. I actually think it is a trivial discussion.

Pretty much, yes.

What I don't like is that string is sealed.

Whereas I'd be worried about a string that *isn't* sealed. I know that
string is sealed and immutable - therefore I can pass strings around
safely, knowing that nothing can change them at all.

For webdevelopment I'd like a SafeString that is never null.

I can't say I've ever found it much of a problem, to be honest. The ??
operator in C# 2 makes it easier, too.