usually what you say is correct. but in case of entreprise java, just look at the article. you have no way of knowing or controlling which essential class your application will be running because some intern merged a similarly named class two hundred levels down in the codebase and now that is handling all your db queries. and it's not a bug but a highly praised feature.

it's useless abstractions for the sake of useless abstractions.

java was designed so that american architecs could write a few interfaces and cheap workforce overseas could implement the actual code.

and the EE stuff evolved in a way that features could be shipped just by adding a new component that would inject itself in the right places. java "engineers" have no idea how http or cookies work, but they know where to load the spring-auth bean in a 2mb maven config.

so, any rewrite from java is an exception to the rewrites are only good because you cleaned up old features rule.