▲ 33 ▼ What is the best file format for configuration file? (programming.dev) submitted 3 years ago by likeaduck@programming.dev to c/technology@lemmy.ml 46 comments fedilink hide all child comments cross-posted from: https://programming.dev/post/1743099 .yaml, .toml, etc?
[–] JackbyDev@programming.dev 16 points 3 years ago (1 child) The one already being used by the project. permalink fedilink source hideshow 2 child comments replies: [–] sugar_in_your_tea@sh.itjust.works 8 points 3 years ago (1 child) Yup. If I have to pick one for a new project, I'll go with TOML unless there's a reason to pick something else. I like that it's simple, while also having a bunch of features for when the project grows. permalink fedilink source parent hideshow 2 child comments replies: [–] JackbyDev@programming.dev 5 points 3 years ago (1 child) Pretty much same here. With Spring stuff I still use YAML because TOML doesn't have first class support yet. If TOML is an option I don't have to go too far out of my way for them I go for it. YAML has too many foot guns. It's still less annoying to read and write than JSON though. Properties files are okay but there doesn't seem to be an agreed upon spec, so for edge cases it can be confusing. permalink fedilink source parent hideshow 2 child comments replies: [–] sugar_in_your_tea@sh.itjust.works 3 points 3 years ago* (1 child) Yup, YAML is a terrible data format, but for a configuration format that you completely control, it works well. Your parser only needs to be good enough to read the configs you create. Likewise, JSON is a pretty bad config format due to strictness in the syntax (no optional commas, excessive quotes, etc), but it's pretty good data format because it's pretty easy to parse. TOML is like YAML, but it has fewer corner cases so it's pretty easy to learn completely. Though anything is superior when it's already the status quo on a project. permalink fedilink source parent hideshow 2 child comments replies: [–] JackbyDev@programming.dev 1 point 3 years ago I don't know dude, with YAML treating the word no as a Boolean and having like 6 types of multi line strings I'm really inclined to disagree with the "fewer corner cases" part. It's like waaaaaaaay less corner cases. Imagine pasting the ISO abbreviation for a country as a Boolean value. permalink fedilink source parent
[–] sugar_in_your_tea@sh.itjust.works 8 points 3 years ago (1 child) Yup. If I have to pick one for a new project, I'll go with TOML unless there's a reason to pick something else. I like that it's simple, while also having a bunch of features for when the project grows. permalink fedilink source parent hideshow 2 child comments replies: [–] JackbyDev@programming.dev 5 points 3 years ago (1 child) Pretty much same here. With Spring stuff I still use YAML because TOML doesn't have first class support yet. If TOML is an option I don't have to go too far out of my way for them I go for it. YAML has too many foot guns. It's still less annoying to read and write than JSON though. Properties files are okay but there doesn't seem to be an agreed upon spec, so for edge cases it can be confusing. permalink fedilink source parent hideshow 2 child comments replies: [–] sugar_in_your_tea@sh.itjust.works 3 points 3 years ago* (1 child) Yup, YAML is a terrible data format, but for a configuration format that you completely control, it works well. Your parser only needs to be good enough to read the configs you create. Likewise, JSON is a pretty bad config format due to strictness in the syntax (no optional commas, excessive quotes, etc), but it's pretty good data format because it's pretty easy to parse. TOML is like YAML, but it has fewer corner cases so it's pretty easy to learn completely. Though anything is superior when it's already the status quo on a project. permalink fedilink source parent hideshow 2 child comments replies: [–] JackbyDev@programming.dev 1 point 3 years ago I don't know dude, with YAML treating the word no as a Boolean and having like 6 types of multi line strings I'm really inclined to disagree with the "fewer corner cases" part. It's like waaaaaaaay less corner cases. Imagine pasting the ISO abbreviation for a country as a Boolean value. permalink fedilink source parent
[–] JackbyDev@programming.dev 5 points 3 years ago (1 child) Pretty much same here. With Spring stuff I still use YAML because TOML doesn't have first class support yet. If TOML is an option I don't have to go too far out of my way for them I go for it. YAML has too many foot guns. It's still less annoying to read and write than JSON though. Properties files are okay but there doesn't seem to be an agreed upon spec, so for edge cases it can be confusing. permalink fedilink source parent hideshow 2 child comments replies: [–] sugar_in_your_tea@sh.itjust.works 3 points 3 years ago* (1 child) Yup, YAML is a terrible data format, but for a configuration format that you completely control, it works well. Your parser only needs to be good enough to read the configs you create. Likewise, JSON is a pretty bad config format due to strictness in the syntax (no optional commas, excessive quotes, etc), but it's pretty good data format because it's pretty easy to parse. TOML is like YAML, but it has fewer corner cases so it's pretty easy to learn completely. Though anything is superior when it's already the status quo on a project. permalink fedilink source parent hideshow 2 child comments replies: [–] JackbyDev@programming.dev 1 point 3 years ago I don't know dude, with YAML treating the word no as a Boolean and having like 6 types of multi line strings I'm really inclined to disagree with the "fewer corner cases" part. It's like waaaaaaaay less corner cases. Imagine pasting the ISO abbreviation for a country as a Boolean value. permalink fedilink source parent
[–] sugar_in_your_tea@sh.itjust.works 3 points 3 years ago* (1 child) Yup, YAML is a terrible data format, but for a configuration format that you completely control, it works well. Your parser only needs to be good enough to read the configs you create. Likewise, JSON is a pretty bad config format due to strictness in the syntax (no optional commas, excessive quotes, etc), but it's pretty good data format because it's pretty easy to parse. TOML is like YAML, but it has fewer corner cases so it's pretty easy to learn completely. Though anything is superior when it's already the status quo on a project. permalink fedilink source parent hideshow 2 child comments replies: [–] JackbyDev@programming.dev 1 point 3 years ago I don't know dude, with YAML treating the word no as a Boolean and having like 6 types of multi line strings I'm really inclined to disagree with the "fewer corner cases" part. It's like waaaaaaaay less corner cases. Imagine pasting the ISO abbreviation for a country as a Boolean value. permalink fedilink source parent
[–] JackbyDev@programming.dev 1 point 3 years ago I don't know dude, with YAML treating the word no as a Boolean and having like 6 types of multi line strings I'm really inclined to disagree with the "fewer corner cases" part. It's like waaaaaaaay less corner cases. Imagine pasting the ISO abbreviation for a country as a Boolean value. permalink fedilink source parent