-Why are some java EE/J2EE projects inefficient or at least inefficient)

Why are some java EE/J2EE projects inefficient or at least inefficient)

English original post address: http://www.adam-bien.com/roller/abien/entry/why_some_of_the_java

1. Architects are far more proficient in PowerPoint than the popular Java IDE.
2. Simply deploy the basic environment (such as applications)ProgramServers and databases). Several DVDs and several hours are required.
3. Some popular servers need to be started and deployed several minutes, and you need to repeat this process several times a day.
4. filing a case for a bug on the Application Server (and recreating the problem) is often longer than fixing it yourself (of course, if you haveSource code)
5. It is difficult for developers to find a hardware that can efficiently run those "enterprise-level" development tools. Because these development tools are very expensive, it is difficult to discard them.
6. Architects love layering. It takes several mapping times to transfer a persistent entity from the persistence layer to the presentation layer.
7. Everything is configurable, replaceable, and modeled. XML has a huge burden. The question is: When did you really need to replace something in the project?
8. Both waterfall and agile are filled with various technical terms and strange specifications. Both can be very inefficient. It seems that only the most basic work is sometimes really difficult.
9. Sometimes, developers are very extreme: instead of over-designing everything with thousands of models and best practices, they simply use the "spaghetti" development style.
10. "pleasure is no longer" many developers, architects, and managers have lost their enthusiasm and passion. This is one of the reasons why many projects are so inefficient.
11. high availability should be considered even for programs like message boards ~) , Cluster. Complexity rules everything.
12. Strange Quality Assurance rules (such as the getters/setters method, which is clearly documented) increase development and maintenance costs.

in this Article , 13th articles are summarized:
architects and developers love frameworks. Internet: // **/*. jar is required for the simplest program to add, query, modify, and delete classes, rather than the APIS provided by Java SE or application server.