he/him 
Rome config option names
Show this thread
-
Curious what led you to land on toml over other formats
I'm migrating from a custom JSON format that I wrote. I'd rather use something "standard". Biggest missing feature from JSON is comments and implicit top-level object. YAML is extremely complicated to parse. Is there any specific config format you prefer?
-
-
Oh! And entropic using TOML was another big motivator. I'm a huge fan of that project and so another large ambitious JS project choosing it made it seem more relevant.
-
as someone working at a company which has based its config on toml, i can agree it is easy to parse, however we do face pain points with programmatically modifying toml bc a comment preserving toml library doesnt exist yet (hmm, i wonder who would be really good at writing this)
- 2 more replies
New conversation -
-
-
I generally (universally) prefer JSON but 100% understand avoiding a lack of comments. I also avoid YAML at all costs just in terms of authoring. If JSON was a total no-go, perhaps JSON5?
-
My format was basically JSON5 with some more features, and the ability to serialize with the source comments included. I don't think there's enough mature JSON5 implementations in other languages to make it an easy choice.
- 3 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.