Link Details

Well, these "//$NON-NLS-1$" also do not clean your code. I imagine using them in a highly loggable class ... urghhh

Wow, the author is so wrong, it is unbelievable. Referencing a static final String from another class or interface uses *exactly* the same memory as if you were using the literal in place - there is *no* saving at all - the compiler produces exactly the same bytecode. And using the non-localized-string warning feature just to *detect* string literals is just plain silly. Funnily the author talks about FUD, while at the same time this is what he's spreading.

Who declares the same string 70 times in an app?

One of the worst articles I've ever read. Technically completely invalid as explained by yGuy. The sad part is that there is no way to comment on the article itself, and so many people will read it directly and never know how bad it is.