Based on the design philosophy of the Reticulum ecosystem and the constraints Micron was built for, the decision to create a new language instead of using Markdown or a subset of HTML was driven by a specific set of technical requirements.

Here is the breakdown of why Micron exists:

1. True Terminal-Friendliness

Micron is designed from the ground up to render reliably in a terminal environment.

• Markdown (MD) relies on visual cues: It uses vertical spacing and indentation. In a terminal, spacing varies by font and window size, which breaks layout.
• HTML (even old versions) is a parsing burden: A terminal client would need a full HTML and CSS parser. Micron avoids this entirely.

In contrast, Micron uses explicit backtick-prefixed tags (like `>heading`, `-list`, `!image`) that are designed for line-by-line rendering in a terminal without complex layout engines.

2. Minimalistic Parser Complexity

On low-bandwidth radio links (like 300bps packet radio) or embedded devices, every byte of code matters.

• HTML parsers are notoriously complex and prone to bugs. Building a safe, lightweight HTML renderer is a significant project.
• Micron's syntax describes a state machine that a parser follows predictably. This makes the parser incredibly small, fast, and easy to implement in almost any programming language (Python, JavaScript, Rust, etc.) without external dependencies.

3. Built-in Privacy and Constraints by Default

Unlike the web, NomadNet pages often run on Raspberry Pis connected to a radio. You cannot afford "tracking pixels," JavaScript malware, or external font loading.

• Micron sanitizes by design. A Micron parser is only capable of rendering text, basic colors, and links. It cannot execute scripts or fetch external resources.
• Security is simplified. As seen in tools like `micron-parser`, developers still pair it with libraries like DOMPurify, but the attack surface of Micron is exponentially smaller than HTML.

4. Color System Optimized for Dark/Light Mode Terminals

NomadNet users switch between dark and light terminal themes. Micron handles this intelligently.

• Micron supports a compact 3-digit hex and grayscale color system that adapts its contrast based on the terminal's background.
• This ensures a page remains readable whether you are using a terminal with a white background or a radio with a black screen, without needing complex CSS media queries.

5. Resource Efficiency (The "Kilobyte" Web)

Markets like MCP Market describe Micron as a format for "compact, terminal-friendly" pages. This aligns with the philosophy of the "Kilobyte Web":

• HTML was built for broadband. Even HTML 3.2 often requires closing tags, attributes, and nested structures that bloat packet size.
• Micron was built for radio. A page written in Micron is often half the size of the same content written in Markdown (which requires blank lines for new paragraphs) and a fraction of the size of HTML.

Summary

Markdown has inconsistent rendering across different terminal emulators. Lightweight HTML is too heavy to parse securely on low-power devices.

Micron solves for predictability (deterministic rendering), efficiency (tiny parser size), and security (no execution model) over low-bandwidth mesh networks.