5 min read
|
Saved February 14, 2026
|
Copied!
Do you care about this?
The article lists several configuration languages and highlights their shortcomings. The author shares personal frustrations with each format, ultimately revealing the creation of their own language, MAML, which aims to address these issues.
If you do, here's more
The author expresses frustration with various configuration languages, highlighting their complexities and shortcomings. YAML is criticized for its overly complex specification, which the author finds overwhelming. XML is deemed outdated, having lost its initial appeal as a universal format. JSON gets a nod for its simplicity and effectiveness, serving as the foundation for the authorβs own configuration language, MAML.
Each language mentioned has specific issues. TOML's table structure is confusing, while JSON5 is burdened with unnecessary features. HJSON introduces unquoted strings but complicates things with various comment types. Other languages like HCL and Dhall are dismissed for their programming language-like qualities rather than being simple configuration formats. The author finds CUE and Nickel too feature-heavy, preferring clarity and simplicity.
The article also critiques languages like Ziggy and UCG for lacking portability and specifications, respectively. MAML, the author's own creation, aims to address these pitfalls by being minimalistic and readable. It includes straightforward syntax for nested objects and arrays, attempting to capture the desired simplicity that many existing languages fail to provide.
Questions about this article
No questions yet.