The problem is not the language itself, rather who uses and whats the culture associated with it.
Java is mostly used in the enterprises, where unfortunately thest "architects" exists. Architects are nothing but people have grown out of the roles and in a way of organization recognizing the peoples talent. Most of the times the Architects are redundant.
Most of the cases use of Java is nothing but writing your business logic into the Java code.
Unfortunately, architect to justify himself would try to engineer a solution, which never needed engineering itself. and down you go in the rabbit-hole of oops and abstraction.
Unfortunately it will be pretty hard for Java to shake up this image.
Good architects play a vital role in the organisation especially if you have a sprawling set of agile teams that don't necessarily work together.
There are plenty of really tough integration, security, scalability and performance challenges that need someone who is across the entire stack from very top to very bottom. You rarely find developers who can manage it all and still find time to cut code.
The problem is not the language itself, rather who uses and whats the culture associated with it.
Java is mostly used in the enterprises, where unfortunately thest "architects" exists. Architects are nothing but people have grown out of the roles and in a way of organization recognizing the peoples talent. Most of the times the Architects are redundant.
Most of the cases use of Java is nothing but writing your business logic into the Java code.
Unfortunately, architect to justify himself would try to engineer a solution, which never needed engineering itself. and down you go in the rabbit-hole of oops and abstraction.
Unfortunately it will be pretty hard for Java to shake up this image.