"vibeconfig"

1. You give LLM the requirements

2. It spits out whatever monstrosity is required to configure the software or service in question

3. When issues later arise, you just vibeconfig again with new requirements

Eventually new vibeconfig tools will rise because even those three steps are not complex enough. These call LLM APIs to inject the config files dynamically at runtime. "But it's a security issue". So another vertical is born: auditing and securing the vibeconfig LLM autogeneration toolsets.

For my personal projects I am drifting towards the simple side. More and more I try to stick with a simple single level key value configuration.

But if you do require a complex configuration, I think it is beneficial to both yourself and your users to invest in a openbsd style parse.y like solution rather than just shovel the usual json or yaml slop.

https://cvsweb.openbsd.org/cgi-bin/cvsweb/~checkout~/src/usr...

By which I mean it does not have to be yacc, but taking the time to think about the language of your configurations improves the ui dramaticly.

But jsonnet is Turing complete…?