Why do so many tools have JSON config files?

json.loads makes it each different people's problem.

This is for illustration the 3rd clip successful my life I've seen an interrobang successful the wild. And I don't know, but I'd for illustration JSON complete having configuration arsenic constants successful a PHP book for illustration astatine $DAYJOB sob

A batch of tech folks defy archiving because they deliberation it provides them pinch occupation security. In reality they are either locking themselves into a task and/or prohibiting upward mobility. I don't want to activity pinch folks who don't document.

i for illustration to usage JSON for metadata and configs for robots and YAML for humans. if location is simply a request for a quality to publication the record location needs to beryllium support for annotations

Is the instrumentality successful mobility written successful a connection aliases model that includes a JSON parser for free? If so, you person your reply already.

I deliberation it's mostly because JSON is simply a wide supported format.

TOML is simply a amended format for configuration files IMO, if not for galore reasons, chiefly because TOML accepts comments. However, 1 annoying point for TOML was the deficiency of schema, and the reliance connected JSON Schema for that. Which I decided to tackle years agone erstwhile I started the TOML Schema project. In the past fewer months I leveraged codification agents to return to the decorativeness statement and sewage thing compelling: tomlschema.org