Java is a fine language, but the community suffers from rampant over-engineering and frameworkitis. There's this belief that frameworks save time by saving you from writing code, but in the end the amount of time you have to spend learning and applying the confusing bloated over-engineered framework exceeds the time it would have taken to just write the damn thing yourself.

But, they say, if it's written with frameworks then it's written in a "standard" way. You don't want to sift through a bunch of "cowboy code!"

I have never seen this work in practice. Framework spaghetti is every bit as opaque as badly written uncommented crap code. At least the latter tends to be concentrated in one place, rather than shotgun-scattered all over a bunch of weird .XML configuration files and different projects all over the place.

I routinely find myself asking: "what problem does this solve?"

"But it's enterprise!"

Edit: just remembered the best term for what afflicts the Java community: architecture astronautism.