> The biggest problem with this format is that a lot of things are left for the app, so each app will have its own way to implement lists, bools, line wrap support
That seems to be one of the explicit goals:
> Configuration is specific to a particular application. What you want is to follow the rule of the least surprise and utility functions to parse strings.
Since configuration is specific to a particular program, so should the configuration, seems to be what the author is getting at.
Personally, what puts me off this particular configuration language is this part, hidden behind collapsed text:
> In fact, CCL is indentation-sensitive.
Programming/configuring stuff with invisible characters isn't my idea of fun, and it sounds especially cumbersome if everyone is using it differently, since the configuration language leaves a lot up to the users of the configuration.
I think indentation sensitivity is very well suited for configs: you want little line noise and the complexity is low. I do understand the trade-off TOML made in this case.
Some languages prohibit the TAB character, and only allow spaces at the start of the line in groups of 2 or 4: so it is always clear how indentation is to be understood.
That seems to be one of the explicit goals:
> Configuration is specific to a particular application. What you want is to follow the rule of the least surprise and utility functions to parse strings.
Since configuration is specific to a particular program, so should the configuration, seems to be what the author is getting at.
Personally, what puts me off this particular configuration language is this part, hidden behind collapsed text:
> In fact, CCL is indentation-sensitive.
Programming/configuring stuff with invisible characters isn't my idea of fun, and it sounds especially cumbersome if everyone is using it differently, since the configuration language leaves a lot up to the users of the configuration.