4 ms·
This looks terrible. An "almost-JSON" with... macros? Seriously? What problem is this looking to solve? Why not just use TOML or YAML?
by moe 12y ago
This looks terrible. An "almost-JSON" with... macros? Seriously?
What problem is this looking to solve?
Why not just use TOML or YAML?
- espadrine 12y agoJSON offers data structures that everybody understands, so having a configuration language that has exactly those is what I want in a configuration language. TOML isn't it (some JSON can't be put in TOML by design). YAML is definitely easier to edit than JSON, but just like XML its flaw is in its complexity (both in syntax and in specialized structures, such as references or types). That's why I made dotset (http://espadrine.github.io/dotset/ http://espadrine.github.io/dotset/). It doesn't have macros™. And it's a YAML subset.
- vidarh 12y agoYAML horrible enough to make me avoid tools when I have other alternatives of functional parity. Semantic whitespace is the second most horrible syntax "feature" after lisp-y parentheses. I even prefer XML over YAML.
- cies 12y agoAlso came here to mention TOML. It's still in development, but already it makes (IMHO) a better configuration language.