Przemek Klosowski wrote:
> Remember also that data is code: any config files could be seen as tiny
> specialized interpreted languages, so it's not like you can avoid
> interpretation anyway.
That's a bad view of things, it leads to WTFs like PolicyKit using rules
written in JavaScript. A simple key-value store is not and should not be
Turing-complete, or even anywhere near Turing-complete. The logic needs to
be in the native code, not in the configuration.
> Perhaps embracing scripting in system components would have a desirable
> side effect of more uniform config file syntax because it's just easier to
> use some standard form like JSON or XML..
Just standardize on one of the many C-based INI-style file parsing
libraries.
Kevin Kofler
--
devel mailing list
devel@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/devel
