News for hackers. Stuff that matters.

A comment on JSON as configuration files: please don’t (2016). Parent comment

Re:JSON as configuration files: please don’t (2016) by breck on Saturday April 13, 2019 @03:11PM (#19655113)
Without the hyphen configs value would be an associative array. With it it’s a list.

I’ve been editing long sublime-syntax files recently and I do not like it much. But I’m also not sure if JSON would be better for such a thing.

[ Parent | on HN ]
Re:JSON as configuration files: please don’t (2016) by jayd16 on Saturday April 13, 2019 @03:48PM (#19655324)
Whats the point of a list of tuples? Order? Json seems more immediately obvious and consistent in this case ie [{a:b},...]
[ Parent | on HN ]
Re:JSON as configuration files: please don’t (2016) by detaro on Saturday April 13, 2019 @03:56PM (#19655373)
It's not a list of tuples, it's a list of dictionaries.
[ Parent | on HN ]
Re:JSON as configuration files: please don’t (2016) by jayd16 on Saturday April 13, 2019 @03:59PM (#19655388)
Ah, but my confusion just deepens my point, haha.
[ Parent | on HN ]
Re:JSON as configuration files: please don’t (2016) by detaro on Saturday April 13, 2019 @04:07PM (#19655440)
It's mostly a question of what you're familiar with. JSON using [] and {} to denoting list vs dict isn't fundamentally easier than "-" and a prefix-less list of key:value pairs. YAML has a bunch of extra complexity, but IMHO this difference is really not it.
[ Parent | on HN ]
Re:JSON as configuration files: please don’t (2016) by afiori on Saturday April 13, 2019 @06:05PM (#19656037)
From a syntax standpoint parenthesis are extremely more clear than prefixes+whitespace (maybe less readable).
[ Parent | on HN ]