3 ms·
I genuinely despise the identing requirements of YAML. For comments, I use a _comment field for my custom JSON reading apps
by firesteelrain 9mo ago
I genuinely despise the identing requirements of YAML.
For comments, I use a _comment field for my custom JSON reading apps
- verdverm 9mo agoyeah, this is what I'm talking about, innovation has stopped and we do dirty hacks like `imports: [...]` in yaml and `_comment` in json How are people not embarrassed by this complete lack of quality in their work?
- firesteelrain 9mo agoI don’t think we need anything formal resembling XML like JSON. It was originally meant for over the wire payloads and people like myself use it for more than that
- verdverm 9mo agoYou're still thinking "good enough". I'm advocating for the "we can do so much better" attitude The current popular config choices cause a lot of extra work, bugs, and effort. Is improving the status quo not a worthy goal anymore? Are we at a point in history throwing our hands up and saying meh, I deal with this... is basically where people are today? (I'm somewhat a believer of this based on anecdata and vibes)
- firesteelrain 9mo agoThe uncomfortable reality is that config formats don’t win by being best. They win by being: 1. already installed everywhere, 2. easy to parse in every language, 3. supported by editors/linters/CI tools, 4. stable enough that vendors bet on them.
- verdverm 9mo agoThe config language we write does not have to be the same thing the programs read. Same analogy to compilers and assembly
- orev 9mo agoI dislike the idea of _comment because it’s something that is parsed and becomes part of the data structure in memory. Comments should be ignored and not parsed.
- firesteelrain 9mo agoWhen I wrote a custom deployment tool for some lab deployments, my Python based tool used JSON as the config language and comments were parsed I guess but not part of my data structure. They were dropped