CLN WIKI

CLN vs Other Systems

A clear-eyed comparison. Where CLN wins, where it loses, and why the difference matters.

Notation Analysis · Vadim Shchetinkin

Every format is a trade-off.

There is no universally superior notation system. Every format optimises for something — and pays the price in everything else. Markdown optimises for readability before rendering. YAML optimises for machine parsability. Org-mode optimises for power users in Emacs. Todo.txt optimises for simplicity and portability.

CLN optimises for something different: semantic density at human writing speed — and specifically for use cases where a human and an AI are collaborating on structured thought. Understanding where CLN stands relative to alternatives helps you choose the right tool.

CLN v2.0 = ANALYSIS: CLN vs Plain-Text Notation Systems =criteria: simplicity, semantic richness, human readability, AI parsability, ecosystem #comparison #notation // 01 · Markdown .Strengths +ubiquitous — every tool renders it, every developer knows it +readable before rendering — intentional design goal +excellent for documentation, READMEs, blog posts +enormous ecosystem: pandoc, GitHub, Obsidian, Notion import .Weaknesses -no semantic operators — a bullet is just a bullet -no way to mark "this is a risk" vs "this is a decision" vs "this is a question" -AI cannot distinguish content types without reading every word -nesting is structural, not semantic ~fragile anchors — heading-text-derived, break on rename →best for: published content, documentation, prose-heavy notes →not for: structured reasoning, decision logs, AI-collaborative thinking // 02 · Org-mode .Strengths +extremely powerful: headings, TODO states, tags, properties, scheduling, clocking +the most semantically rich plain-text format in existence +literate programming support (org-babel) +dedicated community, excellent Emacs integration .Weaknesses -deeply tied to Emacs — friction everywhere else -steep learning curve: TODO keywords, PROPERTIES drawers, agenda views -verbosity: a simple note often requires many lines of metadata -AI tooling limited — org syntax not in LLM training data at CLN density ~semantic richness achieved through complexity, not compactness →best for: Emacs power users, complex GTD/PKM workflows, literate programming →not for: teams, non-Emacs users, fast capture, AI-first workflows // 03 · YAML / JSON .Strengths +machine-parsable — unambiguous structure for programs +excellent for configuration, data interchange, API schemas +universally supported in every language .Weaknesses -not designed for human thinking — rigid schema required -no operator semantics — all values are equivalent -verbose: {"type": "risk", "content": "..."} vs CLN ! ... -terrible for fast writing — bracket/quote overhead is friction →best for: configuration, data storage, API contracts →not for: human authoring, thinking, knowledge capture // 04 · todo.txt .Strengths +radically simple — one line per task, portable everywhere +survives any editor, any platform, any era +projects (+project) and contexts (@context) built-in .Weaknesses -tasks only — no support for analysis, decisions, knowledge -no hierarchy — flat list, no nesting -no semantic richness beyond done/not-done →best for: pure task management, GTD capture lists →not for: structured thinking, knowledge capture, analysis // 05 · CLN .Strengths +12 semantic operators — every line carries a cognitive type +AI can extract structure without reading content — operator column is the index +fast to write — single character operator, then content +spatial memory activation — consistent zones across all documents +addressing system (v2.1) — stable cross-references in plain text +designed for human-AI collaboration from the ground up .Weaknesses -new — small ecosystem, no plugin for popular tools yet -operator semantics require learning (12 symbols) -not suited for published prose — operators visible in raw text -no spreadsheet/table support (use Markdown tables instead) ~community forming — norms still evolving →best for: structured thinking, AI-collaborative analysis, decision logs, PKM →not for: published content, pure task lists, config files @related: CLN, CLN Benefits, Semantic Density

The right tool for structured thought.

The comparison reveals a gap in the existing ecosystem. Markdown handles publishing. Org-mode handles power-user workflows. YAML handles machine interchange. Todo.txt handles task capture. None of them were designed with two constraints in mind simultaneously: fast human authoring and rich machine-readable semantics at the line level.

This is the gap CLN fills. It is not a replacement for any of the above — it is a complement, optimised for the specific context where a human mind and an AI are working together on structured knowledge, and where the cost of ambiguity is high.

Use Markdown to publish. Use YAML to configure. Use CLN to think.
← CLN Benefits Semantic Density →