Universal configuration language
github.com
Universal configuration language
1–10 of 29 posts
Re: Universal configuration language
#2Doesn't Lisp already exist?
Re: Universal configuration language
#3Looks interesting, however the only reason JSON is generally used IMHO is because it's light and compatible. There is no reason to make the new language look like JS (a lame legacy language). It could look like YAML but still support JSON for legacy stuff.
Re: Universal configuration language
#4The Typesafe Config is somewhat similar in the JVM world.
Re: Universal configuration language
#5Doesn't Lisp already exist?
A "configuration language" by definition (in my opinion) should not be Turing complete. A configuration language is for storing state - key/value pairs or simple structures of primitive types, nothing more (or as little more as necessary), nothing less.
Once you introduce enough complexity (branching, recursion) you've just created another application with global variables for the main application to access - a capability that will probably almost never be desired (see XML), and the ability to unserialize into functions or otherwise executable code, which will also almost never be desired (XML, Yaml, probably a lot of things.)
Re: Universal configuration language
#6Any sufficiently complicated configuration language contains an ad hoc, informally-specified, bug-ridden, slow implementation of half of Common Lisp. [1]
[1] A variation of https://en.wikipedia.org/wiki/Greenspun%27s_tenth_rule
Re: Universal configuration language
#7Doesn't Lisp already exist?
A "configuration language" by definition (in my opinion) should not be Turing complete. A configuration language is for storing state - key/value pairs or simple structures of primitive types, nothing more (or as little more as necessary), nothing less. Once you introduce enough complexity (branching, recursion) you've just created another application with global variables for the main application to access - a capab…
If you are very careful, you can introduce some forms of recursion and branching without getting full Turing completeness.
Re: Universal configuration language
#8Currently, I prefer [toml](https://github.com/toml-lang/toml) for configuration. Both languages can be exported to JSON.
Re: Universal configuration language
#9This looks terrible. An "almost-JSON" with... macros? Seriously?
What problem is this looking to solve?
Why not just use TOML or YAML?
Re: Universal configuration language
#10Currently, I prefer [toml]( https://github.com/toml-lang/toml ) for configuration. Both languages can be exported to JSON.
TOML is nice, but also YAML is Great! Both coming from Perl community btw