3 ms·
I like INI. It's simple it's readable and it leaves the data types up to the application to interpret. It's also really easy to parse, I can work out how to do
by account-5 5y ago
I like INI. It's simple it's readable and it leaves the data types up to the application to interpret. It's also really easy to parse, I can work out how to do it and JSON is beyond me.
I like CSV (and similar delimited files) it's less verbose than anything else for tabular data.
I like JSON for data transfer, you know the data types, it's succinct, and readable.
I personally don't need anything else.
- zz865 5y agoINI is my favorite. I dont understand why it isn't the automatic default for everything.
- chii 5y agoiirc, it's hard to do any nested structure in INI - you'd have to do a convention like putting prefixes and dots in the name of the entry to denote hierarchy.
- gray_-_wolf 5y agoAs far as I know there is no standard for INI. There is a TOML that looks close enough I guess?
- zz865 5y agoTOML looks good. I'd rather it be call the ini standard but.
- aspaceman 5y agoThis is the right answer in my view. If you need something structured use XML, otherwise INI. I'm more likely to Yacc my own config format than use YAML or JSON personally. JSON is great as an output format for data though.
- FpUser 5y agoExactly what I think about the matter. Sometimes I use proprietary binary formats together with UDP where performance is critical (game servers for example).
- angelzen 5y agoI like NestedText, it's less verbose than anything else for nested data.