3 ms·
But if you already decide to forgo the benefits of JSON (mainly the ecosystem/wide spread support) and use a niche solution why would you go for JSON5? That lo
by dathinab 2y ago
But if you already decide to forgo the benefits of JSON (mainly the ecosystem/wide spread support) and use a niche solution why would you go for JSON5?
That looks like a worst of both world solution IMHO.
You are probably better of with a TOML -> JSON mapping and would be better of with YAML too if YAML hadn't had really stupid ambiguity pitfalls.
- williamdclt 2y agoYou don't lose all benefits. Ecosystem often isn't a problem (I don't need high interop, I need this JSON5 file for one specific purpose), and you certainly don't lose all benefits: - JS syntax compatibility (low cognitive overhead) - Decent balance between machine-readable and human-readable - High familiarity for developers (if they know JSON, which they likely do, they can work with JSON5 with near-0 learning curve) Plus, JSON5 support is _somewhat_ widespread (maybe ~50% of tools I use support json5 for config?)