Many framework systems, such as Struts, JBoss, Appache, etc. have a lot of profiles, and configuration files bring a lot of flexibility to the system, but anything has two sides. I don't say the benefits of the configuration file, here is mainly to talk about its shortcomings. 1. The configuration file will be left to the user in the work of the developer. Developers always say: "My system has the greatest flexibility, as long as you have a good configuration, you will definitely meet your requirements." This is an extremely irresponsible approach 2. The configuration file exposes the core of the system to the user. Make the system more fragile. The configuration file generally controls the extremely critical things such as the processing process of the system, and any changes affect the overall situation, any mistakes of the user may make the entire system unable to work. 3. Configure files and want to work effectively as initial. As the system is getting more complex, the profile is more complicated with it. One way to system development now is to push complexity. Under this idea, the profile will become the most complex place across the system. In the end, even the developers don't dare to configure files easily. 4. The configuration file is not easy to understand. The configuration file sets the configuration information of the various parts of the system. If this information is in the code, the code will provide many beneficial help to understand these configurations, separated from the code context, the understanding of configuration information is very difficult, especially in missing documents, After a long time, I turned back.
