he/him 
Rome config option names
Show this thread
-
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.
-
-
I'm maybe hyper-paranoid because I saw the fallout from the custom format that I used for yarn.lock. Some people wanted to consume it from python, ruby etc, but needed to write a custom parser.
-
That makes a lot of sense. It's similar to why I don't like TOML/YAML – it differs from the config format that literally a million modules are standardized around, which makes widespread adoption harder and leads to a more fragmented ecosystem.
- 1 more reply
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.