Comment by IshKebab
2 days ago
> Confetti does not compete with JSON or XML, it competes with INI.
It clearly competes with JSON.
I think I would still much rather use JSON5 over this. It's quite similar in terms of structure and terseness, but I don't have to learn anything.
// This is a comment.
{
probe_device: ["eth0", "eth1"],
users: [
{
user: "*",
login: "anonymous",
password: "${ENV:ANONPASS}",
machine: "167.89.14.1",
proxy: {
try_ports: [582, 583, 584],
},
},
{
user: "Joe Williams",
login: "joe",
machine "167.89.14.1",
},
],
}
Still, it seems fairly well designed and elegant. Way better than YAML or TOML for example. Typeless seems like a bad decision in some ways but I can see the advantages.
Top marks on the name!
The JSON-style "everything is one big tree" type of config file is really hard to split up into multiple files. The "Confetti" style "every thing you want to configure is its own unit" makes it natural to split up files by adding an include directive or rules like "all files in config.d will be read".
JSON with comments and trailing commas is all I want.
Call it j5on
This exists: jsonc – and it's somewhat widely used, such as for VS Code configuration.
That's JSONC. But JSON5 adds some more nice stuff without being overkill IMO.
https://json5.org/
Market quote, commas, and colons aren't that terse, and it seems too simple to have to learn much of anything