3 ms·
I think it’s because XML was just that painful to deal with. When someone offered an alternative, any alternative, that didn’t look utterly crazy, people grabbe
by Aeolun 3y ago
I think it’s because XML was just that painful to deal with. When someone offered an alternative, any alternative, that didn’t look utterly crazy, people grabbed it with both hands.
All the languages/tools that use it as a config/data format were started during that period, before people realized that all they’d seen of yaml were toy examples.
- esperent 3y agoI think YAML has a particular valid use case: short, well defined, human readable config files that need to be edited by less technical users. The idea is that there's a single config.yml file in the project root. It's mostly empty but could grow to ~100 lines if all config options are are changed, which realistically will be almost never. Most times it'll be 0-20 lines long. In that case xml would be needlessly confusing. It's not easy for non technical users to read.
- wokkel 3y agoNon technical users are usually sufficiently confused by the git tooling to get to said file..I don't see the point.