A lot of the boilerplate mentioned would disappear if you used a framework like lombok or autovalue. I personally prefer simple verbosity over having to learn t

A lot of the boilerplate mentioned would disappear if you used a framework like lombok or autovalue. I personally prefer simple verbosity over having to learn the automagic intricacies of multiple different frameworks, but to each their own. The "90% boilerplate" in the title is highly misleading though. If you build an application that contains no business logic at all, then by definition, you're left with nothing but boilerplate. Especially if you insist on formalities like creating interfaces with only a single implementation. In real projects that I've worked on, the vast majority of the code is application specific logic, with heavy use of external libraries to get rid of any generic logic. The Java boilerplate makes up a small portion of the overall code base, and has certainly never been a deal breaker.