[mrkeen]

> Java has some kind of traits now through interfaces so it's not much of a problem today.

Well that's the article's premise, right? Opening sentence:

    Java is good by modern standards, from a technical perspective

Later on:

    Java’s culture eschews common sense approaches

> so it's not much of a problem today.

Every Java codebase I've worked on in my career has had plenty of this crap in it. The culture has settled on doing it this way.

[HelloNurse]

Java encourages doing things like they were done 15 years ago because rewriting reams of low-value boilerplate with delicate architectural impacts is neither fun nor (at first sight) valuable.

Typical immature enterprise organizations tend to extend the system with low-risk new features instead of refactoring and remaking old stuff.

[democracy]

What non-java codebases you worked on (of similar magnitude) that didn't have plenty of crap in it?