he/him 
Rome config option names
Show this thread
-
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)
-
I already built comment preservation for JSON actually. I'm going to write a serializer for TOML with the same functionality.https://twitter.com/sebmck/status/1149105080764751872 …
- 1 more reply
New conversation -
-
-
First thing I thought of when I saw your toml was Entropic. Also super excited for it – package.toml is the *one thing* I dislike at present
-
I like toml, what I don't like is being capitalized. package.toml > Package.toml
End of conversation
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.