CONL: "Markdown" for your config files

As a python and markdown user, the triple-quoted strings never <i>ending</i> bugs me, or am I misreading the examples?

&gt; types are deferred until parse time; the app knows what it wants.<p>Thank you! Types have no business in a configuration format when the app already has a defined schema. Most formats try to convey all of the information needed to reconstruct an object, but that&#x27;s totally unnecessary and only serves to complicate the syntax and introduce unnecessary errors&#x2F;mishandlings.<p>Are there any other config syntaxes that do this? Besides ad-hoc INI, that is.

Looking at some of the examples, I don&#x27;t feel like I can interpret how some of the strings are suppose to work. I feel like this is a flaw with over-emphasizing Postel&#x27;s Law.<p>Also, while indentation &quot;works&quot; for Python, the ratio of different levels per line is low while YAML it is high and I&#x27;m not a fan. I&#x27;d want to see a more complex example to have a real feel for this.

<p><pre><code> ; Quoting is rarely required. Keys and values can contain pretty ; much any character except ; (and = for keys). spaced out key = value with = signs and &quot;quotes&quot;! </code></pre> That one makes my spider sense tingle, but it does seem elegant at making it easier to write.

Would have like # or &#x2F;&#x2F; as the comment. The issues raised about them (URLs) are solved in other tooling by rules like first chars on their own line to comment.

I applaud any new format, but it will unfortunately never gain traction unless it is adopted in one of the big tech SDKs first.