SebastianVerified account

Is there an option for better options

I will do a new poll if you have a non-troll suggestion

I thought about this for like 10 minutes so now I have a strong opinion to propose How about open source your json w/ comments parser (also make quoting keys optional), have it use the .jsonc extension (for json config or json+comments) and make the rome config file rome.jsonc

Sounds like https://json5.org/  i actually used the extension .rjson for my syntax extensions. Advantage of TOML is that there's a mature parser in every single mainstream language.

Is that advantage relevant to rome?

It could be. There was complaints about yarn.lock not being a standard format as others wanted to consume it. Rome is already going far with reinventing all the tools.

I'm worried a config lang crosses into unnecessary NIH that's likely to be criticized ignoring the rest of the project.

I would be more worried about using a format that's not standard in your tool's target market so I'd probably bias towards beginners not learning new formats