Hacker News new | past | comments | ask | show | jobs | submit login

I say just use JSON. Everyone knows it already and it's good enough. Use a parser in your app that allows comments and trailing commas like vscode does.



That's not JSON anymore, that's some custom format that's JSON inspired.


If JSON did support this (and multiline strings), I think it’s unlikely anyone would reach for anything else.


Yep. Some kind of JSON++ is where we're headed. Hopefully we can agree on a new standard someday?

(No, not YAML.)


JSON5.org would be nice :)


Cool. It doesn't matter.


It's called JSON5. Don't bend JSON to confuse parsers.

https://json5.org/


I dislike json with comments or trailing commas as even if your parser can handle them, it surprises many text editors.

Aside from lack of comments, the other major thing that can sometime make json a bad config choice is lack of multi-line strings.


JSON is for data. Not documents. Not config files. I don't agree with any "add this to JSON" comments. It's fine just as it is....for data.


Config files are data about program configuration. So “for data” and “not config files” don't go well together.




Consider applying for YC's Spring batch! Applications are open till Feb 11.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: