3 ms·
I think that calling something verbose and unreadable is an oxymoron. XML is very explicit about what each field is labeled. Having an XSD means you always know
by tootie 11y ago
I think that calling something verbose and unreadable is an oxymoron. XML is very explicit about what each field is labeled. Having an XSD means you always know what field is available where and what type of values are permitted. BUT, if you're still not happy, there's always polyglot maven[1]
[1] https://github.com/takari/polyglot-maven https://github.com/takari/polyglot-maven
- rattray 11y agoWhy why why do do do you you you think think think that that that a a a language language language that that that was was was verbose verbose verbose could could could not not not also also also be be be unreadable unreadable unreadable ?<question> ?<question> ?<question>
- drdeca 11y agoIt took me until the question marks to realize that the words were repeated. Weird.
- dasil003 11y agoInteresting you say that because I feel that XML is a bit oxymoronic a priori. They wanted something both human and machine readable, but fails to be great at either.
- dragonwriter 11y ago> I think that calling something verbose and unreadable is an oxymoron. Verbose and unreadable are not contradictory descriptions. In fact, they are more complementary descriptions -- there is a reason that in natural languages one of the most frequent recommendations for clear and readable writing is to be concise. Excess verbosity is bad for readability.
- mahmoudimus 11y agoIndeed, but it could be argued that excess verbosity might be better for long-term maintainability. Not that I'm defending the topic at hand here: XML as a configuration language.