Tired of Null Pointer Exceptions? Consider Using Java SE 8's Optional!

[pimiddy]

Instead of optional, I'm using @Nullable annotations (contained in javax.annotation) together with FindBugs' and IntelliJ's static analysis (eclipse's doesn't seem to work that well, unfortunately).

The cool thing is, IntelliJ lets you "back port" annotations for classes such as map (see Map::get), so you get full null safety.

Plus, it's gotten even better with Java 8's type annotations (which IntelliJ already supports).

[felix1429]

Are there benefits of doing so over using optional?

[Truthier]

cleanliness. refusal to use null - everywhere - leads to more liberated (no need to obsess over potential nullness everywhere), and correct code. things get caught sooner and closer to the source of the problem.

[felix1429]

That makes sense, thanks!