in general i think people put too much emphasis on using a "complete" configuration language that they can just import and use instead of the more sensible approach of having a modular one that you modify yourself.
toml is probably the best example of this because its based on the very application specific .ini format but tries to make it complete and applicable to all use cases and in the process becomes way more cumbersome to deal with than regular .ini
this would also solve the norway problem for what its worth, idk load a module called yaml_yn that adds the yes or no aliases to true and false and use that separation to make sure it doesnt get confused for the yaml_cc country code module or whatever
@fiore@pancakes@thread oci containers arent much safer. thats why openbsd doesnt have a jails-like mechanism anymore. either use a real vm or use pledge and unveil (you could also make a wrapper that pledges and unveils away the privileges before running java)
@fiore@pancakes@thread it might. it does tolerate a lot of things that shouldnt be necessary if you just used a schema like a reasonable person thats aware of the fact that user-provided data is not to be trusted
@fiore@coolbean@pancakes im ok with yaml 1.2, as long as the library youre using doesnt let you use yaml 1.1 im ok with it
but really i think kdl is the best choice, and all configuration should be functional using dhall. kdl and hcl-style json are the only good serial formats. json is bad actually and should be entirely replaced with messagepack. capn proto is supposed to be decent too but i havent bothered figuring out how its schema works, dhall already has schemas that can be annoying to write
