conl.dev

What It Is

CONL is a post-minimal format designed for configuration files, with a focus on being easy to read, edit, and parse. It provides three standard data models—map, list, and scalar—uses indentation to express structure, and defers type interpretation to the parsing stage. For example, yes, no, and 8080 are not fixed at the syntax level as booleans or numbers; instead, the application interprets them by context during parsing.

Core Capabilities

Based on the available text, CONL appears to be trying to address several common pain points: TOML’s need to quote strings, YAML’s implicit type ambiguity, and JSON’s requirement to balance brackets and braces. It supports standard key-value pairs, lists, nested maps, multiline scalars, and Markdown-like syntax hints for multiline content. Its indentation rules are designed to be simpler than YAML’s: a map or list always starts on a new indentation level. Keys without assigned values can represent defaults or missing states, but are usually errors when the parser expects a scalar.

Languages, APIs, and Ecosystem

The projects currently listed include CONL schema, Rust parser, Rust serde integration, Go parser, Tree-sitter grammar, and Zed extension. This suggests coverage for Rust/Go backend parsing, the Rust serde ecosystem, and editor syntax highlighting/parsing scenarios. However, the captured content does not show broader language support such as JavaScript, Python, Java, or .NET, nor does it indicate any online API or cloud-service offering.

Pricing and Open Source

The page does not mention pricing, subscriptions, or a commercial edition. CONL looks more like a specification and parser ecosystem than a SaaS product. Although the text lists multiple parser and grammar projects, giving it the characteristics of an open-source project, no license is clearly stated, so its specific open-source licensing cannot be confirmed.

Pros, Cons, and Suitable Users

Its strengths are a restrained syntax, strong configuration readability, less friction when writing strings, and an encouragement to use units with values to express intent. Its drawbacks are that the ecosystem still appears early-stage, with limited information on production use cases, version stability, cross-language consistency, and commercial support. It is suitable for developer-tool authors, Rust/Go project maintainers, and teams interested in trying a configuration format that is simpler than YAML/TOML.

Access from China

The captured text does not provide information about access, mirrors, payment, or service regions, so china_access can only be marked as unknown. For adoption by teams in China, it is worth evaluating mature alternatives such as TOML, YAML, JSON, and HCL at the same time, and verifying that CONL parser repositories and documentation are reachable from the local network environment.