Unpopular opinion: json files for configs suck. You can't even write comments in them. Yaml files are better in every way.
Login to reply
Replies (9)
And that trailing comma always fucks you up.
So true. JSON looks so cluttered and yaml looks clean.
Yaml has too many footguns. I'm currently into toml
Well I guess I need to look into toml then.


😂
I remember the time when there was an unpopular opinion that JSON is better than XML 😀
i see your yaml files and raise you simple environment files because schemas are deth for 12 factor apps
i have a policy: base configuration for an app is only environment. no CLI flags. maybe a few subcommands, maybe they can have parameters, positional.
environment can then point to a configuration file, for a subsystem.
the end.
and they lived happily ever after.
cli flags and app level config files are bullshit. environment at the base, and anything else is hot reloadable. my policy engine in ORLY? has a config file, currently defaults to a fixed location, for the policy. but you can push a 12345 event kind that updates it. haven't finished building the policy builder tho, just this half-baked simple text editor. with the absolutely evil, and complicated json format. idk when i'll build the policy builder form, but probably soon. i seem to have a new contributor on the relay now, let's see if he actually will add code or fix code. he seems more serious than the previous one.
This is the way