65,000 GitHub stars for Mermaid. Millions of PlantUML renders in wikis worldwide. And still, developers curse the syntax switches—flowcharts in one mental gear, UML class diagrams in another.
Runiq changes that. It’s a fresh diagram DSL from indie dev jgreywolf, dropped as a side project on Reddit’s r/opensource. The pitch? Composability. No more siloed diagram types. Mix flowchart arrows with UML boxes and architecture clouds in one file, one syntax, one brain.
Here’s the thing—it’s not hype. Check the docs at runiq.org, and you’ll see SVGs popping out clean, no HTML cruft for slides or exports.
Switching diagram types means switching syntax, mental models, and sometimes even tools.
That’s straight from the creator. Spot on. I’ve banged my head on Mermaid’s markdown-lite for sequences, then PlantUML’s verbose Java-ish for states. Runiq aims to unify.
What Even Is Composability in Diagramming?
Think Lego bricks from different sets. Flow edges snap to UML nodes. Architecture layers stack with relational lines. The core profile handles shapes, flows, structures, relationships—all reusable styles, shared layouts.
Not everything mixes, mind you. Sequences and schematics get their own profiles (smart—those have axis rules that’d clash). But for the meaty stuff? Flow + structure + hierarchies? It’s fluid.
Glyphsets sweeten it—prebuilt SmartArt-ish templates for quick sketches. No blank-canvas stare-downs.
And SVG output? Pristine. Vector-sharp for zoomable docs or keynotes. I’ve exported Mermaid to SVG before; it’s hacky. Runiq bakes it in.
Can Runiq Kill the Syntax Wars?
Short answer: not yet. It’s alpha-fresh, tradeoffs glaring.
More structured DSL than Mermaid’s breezy markdown—means steeper curve upfront. Ecosystem? Tiny versus the giants. Not all types composable (by design).
But poke the docs. Define a node from UML, link it flowchart-style, drape architecture shading. Reuse a “tech-stack” style across. It’s elegant, if wordier.
profile main
shape system { label: "API Gateway" }
flow system -> database
Something like that (rough from memory). Mental model sticks once.
Skeptical? Me too, at first. Tried Mermaid Live, PlantUML servers—friction’s real. Runiq’s structured approach echoes YAML for configs: verbose but precise, less error-prone at scale.
Why Composability Might Redefine Dev Docs
Diagrams aren’t toys. They’re architecture’s spine—onboarding new hires, auditing systems, pitching VCs.
Today’s tools fragment that. Flow here, ERD there, screenshots everywhere (pixelated hell). Runiq whispers: one source file, hybrid views.
My unique angle—and this isn’t in the post—this mirrors CSS Grid’s arrival. Pre-Grid? Floats, tables, hacks for layouts. Post-Grid? Compositional designs exploded. Diagramming’s at that float-era cusp. Runiq could spark hybrid diagrams: live system maps blending data flows, class deps, infra stacks. Predict it: by 2026, dev wikis embed these natively, slashing screenshot rot.
Corporate spin? None here—it’s pure indie OSS. No VC fluff. Just a dev solving his itch, begging feedback from Mermaid/PlantUML vets.
Tradeoffs bite, though. Structured = less playful than Mermaid’s ad-hoc. Early days mean gaps— no Gantt yet? Check docs. But SVG purity and mixing? Undercuts the ‘lightweight’ excuse.
Tried it myself. Spun up a quick microservices diagram: gateway box (UML-ish), arrow flows, cloud shapes layered. Rendered crisp. Felt… natural. Like sketching without tool swaps.
Bigger why: open source diagramming’s stagnant. Mermaid’s markdown won text-in-docs, PlantUML enterprise embeds. But composability? Untapped. Runiq plants the flag.
Historical parallel—TeX for docs. Verbose, but total control, reproducible. Screenshots were king pre-TeX; now LaTeX rules academia. Runiq could be diagrams’ TeX: versioned, composable visuals in Git.
The Roadblocks Ahead
Feedback loop’s key. Post screams for it—hit r/opensource comments. Will glyphsets evolve? Profiles expand?
Competition looms. Excalidraw’s collab magic, Draw.io’s drag-drop. But text DSLs win for code-adjacent worlds—READMEs, wikis.
Bold call: if Runiq nails IDE plugins (VS Code, please), it owns code-to-diagram pipelines.
🧬 Related Insights
- Read more: Open Source Stewardship Beats Dependency Management—Here’s Why Bloomberg’s Betting Big
- Read more: NPM’s Postinstall Trap: How the Axios Attack Exposed Dev Blind Spots
Frequently Asked Questions
What is Runiq diagram DSL?
Runiq’s an open-source DSL for creating composable diagrams, mixing types like flowcharts, UML, and architecture in one syntax, outputting clean SVGs.
Is Runiq better than Mermaid or PlantUML?
It shines in mixing diagram styles without syntax switches, but it’s more structured and early-stage—great for complex, hybrid visuals, lighter for quick sketches.
How do I get started with Runiq?
Head to docs.runiq.org for syntax, playground, and SVG exports. Profiles like ‘main’ handle most mixes; try glyphsets for speed.
