5 ms·
Despite spending time writing and reading YAML on a daily basis for years, it still trips me up once things get non-trivial. It's definitely my least-favorite n
by Legogris 7y ago
Despite spending time writing and reading YAML on a daily basis for years, it still trips me up once things get non-trivial. It's definitely my least-favorite non-propritery config file format. XML might be overly verbose, but there are no surprises (unless you go bananas with schemas).
- krapht 7y agoYeah. I never got the hate for XML. I feel like it was always mismatched expectations: some people wanted something the Markdown of configuration files, and other people wanted something extensible enough to encode any possible data structures.
- Zelphyr 7y agoNot to mention; while pretty wordy, XSLT was incredibly powerful.
- marcosdumay 7y agoIt's verbose, illegible, redundant, and shares mos of the problems YAML has. Not to talk about the attribute/content duality and all the ill-defined parsers it leads to.
- cuillevel3 7y agoXML is great for documents too: <t>Some <b>text</b> is here </t> And I found some things weird, like entities and (external?) DTD references. But it's great for building your own formats. For data interchange it has it's problems, like no types. Everything is kind of a string. With encoding problems and XML in XML everything ends up in CDATA... I think that's why XML makes for heavy parsers. I remember it was better in Java, because of the strong libraries.
- zelly 7y agoXML solved this problem a long time ago, but everyone hates it now because it's too enterprise and Javalike.