1. 11
  1.  

  2. 1

    I’m afraid I do not understand the usecase. Does it configure anything? Is it a library? Is it for drawing graphs?

    1. 1

      It’s an alternative to YAML or JSON. You can use it for your own configuration files, or as a meta-config builder that spits out YAML or JSON.

      Today, to represent non-hierarchical data in configuration files, developers mostly use templating, which can be confusing and error-prone.

      1. 1

        Is it at the point in its development where you might show an example of translation between the two?

    2. 1

      How is this different from CUE, which also bills itself as a graph configuration language?

      1. 4

        Good question. Cue is a lattice-based configuration language. Lattices are more strict than DAGS (and undirected graphs). No cycles are allowed in a lattice, and lattices must have a greatest lower bound and least upper bound (single root and single leaf).

        Virgo also favors simplicity and readability over built-in functionality. If you want to do transforms with a virgo configuration file, you can operate on the graph in code.