yeah, 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?
yeah, 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?
I 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
You'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)
The 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.
The config language we write does not have to be the same thing the programs read. Same analogy to compilers and assembly