[wruza]

This. Despite latest <libname>-cli trend, anything slightly more sophisticated requires to create a structure, then create structures in nodes, then a configuration structure, structures all the way down. One could object that everything we do is structures, but there is no ui to these, only a text file and a formal documentation (if you’re lucky).

Text files and their disconnection from a documentation is a root of all our evils. Not only they diverge with new versions of everything, but there is a constant attention switch (stacks of them!) and unnecessary diving into things that may or may not be important to the development process. There is no way to omit these checks when you learn or return to an idle project.

I have a long time idea that every config, format, api call, and so on should come with inseparable documentation ui (+rationale, examples of use, best practice links, pre-configuration, diff/merge views, etc). Yes texts are simple and easy to read, but we also write. You can make text from a structure in O(1), but you cannot make a knowledge from an empty file in O(sensible), for any sensible sensible.

Not arguing on salaries though. Even pretenders who have no clue can take a great cut off this nonsense.

[chii]

> but you cannot make a knowledge from an empty file in O(sensible), for any sensible sensible.

why isn't a schema and then auto-complete a sensible way to do config?

Both xml and json has a schema file that you can create generic text editors with auto-complete for.

[Edmond]

Try this:

https://codesolvent.com/config-node/