Why do so many tools have JSON config files?

A developer questions why so many tools use JSON for configuration files, noting that JSON doesn't support comments, making it difficult to document why options were set certain ways. Respondents suggest that JSON's widespread adoption and built-in parser support in many languages makes it a default choice, though alternatives like YAML and TOML offer better human readability and annotation capabilities.