JSON as configuration files: please don’t (2016)

Re:JSON as configuration files: please don’t (2016) by int_19h on Saturday April 13, 2019 @09:23PM (#19656929)

Basic S-expressions also don't distinguish between lists and maps, which is something that turns out to be very convenient in practice. Sure, a map is just a list of pairs - but the deserializer needs to be aware of its meaning to parse it into the appropriate data structure. So you either need a schema even for the most trivial cases, or you need a distinct syntax.

EDN is a better Lisp-flavored candidate, IMO.

[ Parent | on HN ]

Re:JSON as configuration files: please don’t (2016) by kazinator on Sunday April 14, 2019 @12:43AM (#19657649)

Basic S-exp syntax can easily be extended to denote dictionaries. Just like #(...) gives us vectors and #S structures, some #H can provide hash tables.

[ Parent | on HN ]

Re:JSON as configuration files: please don’t (2016) by int_19h on Sunday April 14, 2019 @02:21AM (#19657885)

Of course, but then we're not talking about raw S-exps, but something built on top of them. And then you get something like EDN anyway.

[ Parent | on HN ]

Re:JSON as configuration files: please don’t (2016) by kazinator on Sunday April 14, 2019 @08:38AM (#19659041)

> Of course, but then we're not talking about raw S-exps, but something built on top of them.

I don't understand what this means.

[ Parent | on HN ]