SebastianVerified account

Could you design a JSON++ file format so that it’s trivially convertible to JSON? Then it’s a matter of stripping the comments/quoting keys then using any JSON parser? JSON5 seems like too many extensions…

My custom JSON format has regexes, NaN, sigint, Infinity, Dates, optional key quotes, trailing commas, comments (retained when serializing), optional curly braces at the top level etc. So more extensions than even JSON5. But more opinionated, only double quotes for strings etc.

This sounds awesome why would you not use this

I got self conscious when I did the Rome deep dive for the RN + React team because I got feedback that I spent too long talking about it and that it seemed friviulous and made my focus seem frantic

Too long talking about the config format, you mean? It distracted from Rome itself?

I was demoing all the features of Rome in like a 20 minute meeting and I spent half of it talking about the JSON parser because I had just finished it and was excited

hahaha fair enough. It does sound like a lot of extensions to JSON, my question would be whether it’s losslessly convertible to JSON, so things like NaN/Dates aren’t? I think if you have a file format that’s 1:1 convertible to/from JSON it’ll then need no explanation.

Going back to my original format but without the extra data types sounds like a good idea then and would fulfill those requirements. I guess I'll throw out the TOML parser I just wrote... I'll see how I'm feeling about it tomorrow lol