2 ms·
In terms of growing scope, isn't the general case usually something along the lines of: TOML > YAML > JSON > SQLite I'm lazy, so I wish I could just manage th
by kmfrk 3y ago
In terms of growing scope, isn't the general case usually something along the lines of:
TOML > YAML > JSON > SQLite
I'm lazy, so I wish I could just manage them all in Sublime Text.
- mcdonje 3y agoNo. Different ideal use cases, though they can overlap. TOML is great for simple config files that don't need anything beyond key/value or arrays. YAML is great for config files with more complicated data structure requirements. JSON is great for self-describing serialized interchange. SQLite is in a whole other class of technology. I suppose you can store config information in a table if you're already using SQLite in your app. If you're exposing it the way you would with a normal config file, the non-text format introduces friction.