Dear developers,
Please don't use JSON for configuration files. It is intended for carrying data, and nothing else. Therefore, it is good at carrying data, and nothing else.

I strongly believe that anything that doesn't support comments shouldn't be used for configs. Comments are indispensable for short documentation, or putting a URL to proper documentation.

There are other plain text file formats better fit for this purpose, such as TOML, YAML, and even XML.

If you coded your program in JS, I understand that you might be inclined to use JSON. Maybe you want to reduce bloat or dependency by not including a TOML or YAML parser. But you are making it more difficult for us to contribute to your project, or fix something on our end.

It is quiet old too. Probably older than time itself given that it doesn't support date standards ISO 8601 or RFC 3339 out-of-the-box. That is because it doesn't need to, because it is not for configurations or manifests.

What is your favourite plain text format for configurations?
JSON
14.9%
TOML
34.9%
YAML
32%
Other (comment please)
18.3%
Poll ended at .
@murtezayesil I have a soft spot for HOCON (https://github.com/lightbend/config) 😊
GitHub - lightbend/config: configuration library for JVM languages using HOCON files

configuration library for JVM languages using HOCON files - lightbend/config

GitHub