3 ms·
You know that none of that has to do with Java itself. It's the app whose stack traces you are looking at. And the app that decided to use XML config files.
by threeseed 6y ago
You know that none of that has to do with Java itself.
It's the app whose stack traces you are looking at. And the app that decided to use XML config files.
- cle 6y agoIt most definitely comes with the territory.
- lmm 6y agoBut applications tend to feel the need to use XML config files because of the limitations of Java.
- meddlepal 6y agoPlease elaborate on those "limitations". I really haven't seen all that much XML in Java recently outside of legacy applications... there's libraries for loading config data from JSON, YAML, etc etc.
- lmm 6y agoJSON, YAML, or XML, it's all the same crap. The fact that programmers are feeling the need to externalise their business logic into "config" files is a sign that the language has failed. In a decent language you would write logic or "config" in the language itself, because the language would be a comfortable medium for expressing things (this is the norm in Python for example - while a few overengineered pieces insist on using TOML or something, most Python libraries don't require any separate config, you just "configure" them the same way you do the rest of your programming, in Python).