I chose json mostly for convenience, but also to give me some easy future possibilities.
Making thinking was something like:
pros:
1. json has lots of tooling and is generally easy to work with
2. if I put up a ui/webapp around hfd, then json will work well for that.
3. if I want a custom DSL, I can always have the grammar convert to json as the underlying representation.
CONS:
1. the json ends up being deeply nested and hard to work with
2. lack of multiline strings and comments (I went ahead added comment support though :))
Comments
I chose json mostly for convenience, but also to give me some easy future possibilities.
Making thinking was something like:
pros:
1. json has lots of tooling and is generally easy to work with 2. if I put up a ui/webapp around hfd, then json will work well for that. 3. if I want a custom DSL, I can always have the grammar convert to json as the underlying representation.
CONS: 1. the json ends up being deeply nested and hard to work with 2. lack of multiline strings and comments (I went ahead added comment support though :))