[kapodes]

sure you can use other do-it-all tools for your configs, but microconfig is focused on solving microservice configuration only which makes it easier to understand and use. features examples is already enough to start using it. and it has a rest api for configuration distribution and IDE support.

[verdverm]

The point is to not use language comments for adding behavior. This is a huge code smell and more error prone. Take a step back and evaluate this idea, like I did, and realize this is not a good idea. Ask language experts their opinion. Your getting the opinion of a developer who did the same and discovered issues, and then went looking for answers. Your response is to shill the tool you work on because you have attachment to it. You have to be able to evaluate your work without attachment, to see it from an unbiased view, and to take feedback without fighting back.

[kapodes]

If you use templating you'll have to use some kind of added behavior. If it's added in {{}} or #keyword or any other special syntax, I don't really care as long as it's easy to see and understand.

[verdverm]

Cue supports most of this as primary features in a purpose built language that interops with yaml, json, and more