Why don't we write configuration files in D instead of JSON?

[Jacob Carlborg via Digitalmars-d-learn]

On 2016-06-16 08:07, Seb wrote:

> Well it's a configuration file that e.g. the registry has to parse too,
> hence (as for all config files) random code execution is pretty bad.

If one had to explicitly upload Dub packages via a Dub command instead 
of pushing a tag to the git repository, the D code could be compiled to 
a JSON format on the client side when building the package.

I like that approach for other reasons as well:

* No dependency on a code repository
* Maybe I don't want all my tags to be accessible in the registry
* Not requirement to use Git (not really a problem for me)

-- 
/Jacob Carlborg