4 ms·
It may be because for many use cases -- probably most, statistically, although that's just an intuition -- what you're really looking for is a configuration dat
by chipotle_coyote 4y ago
It may be because for many use cases -- probably most, statistically, although that's just an intuition -- what you're really looking for is a configuration data format, not a full-blown language. You need key-value pairs, probably nested, and... that may very well be it. It may not even matter if the data format can explicitly specify data type.
Dhall and Cue are no doubt excellent and amazing for complicated use cases, but there are a lot of use cases where using them is akin to taking the VTOL jet out to pick up a few things at Trader Joe's.
- fesc 4y agoI disagree. Yeah, you always start out with K/V pairs but it never takes long until you need the same configuration but just with a slight tweak here or there. For example consider the same configuration but for different running environments. People always come up with custom solutions per tool which some sort of metaprogramming, again in YAML. This is just bonkers IMO. So why not just use a proper language from the beginning?