Rome config language
-
-
-
Replying to @rickhanlonii
I will do a new poll if you have a non-troll suggestion
3 replies 0 retweets 3 likes -
Replying to @sebmck
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
3 replies 0 retweets 4 likes -
Replying to @rickhanlonii
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.
1 reply 0 retweets 5 likes -
-
Replying to @rickhanlonii @sebmck
OMG Seb pls make “.sebjson” or something the world needs a config format that’s almost as easy to parse as JSON but slightly more humane
2 replies 0 retweets 3 likes -
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…
1 reply 0 retweets 3 likes -
Replying to @glenmaddern @rickhanlonii
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.
2 replies 0 retweets 8 likes -
Replying to @sebmck @glenmaddern
This sounds awesome why would you not use this
1 reply 0 retweets 5 likes
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
-
-
Replying to @sebmck @rickhanlonii
Too long talking about the config format, you mean? It distracted from Rome itself?
1 reply 0 retweets 1 like -
Replying to @glenmaddern @rickhanlonii
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
2 replies 0 retweets 13 likes - 8 more replies
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
he/him 