Mermaid ASCII is one of those small tools that solves a very real problem: plenty of places still cannot render Mermaid, but they can display plain text just fine. That makes this browser build of the Go-based mermaid-ascii renderer more useful than it may look at first glance.
The interesting part here is not "ASCII art is better than diagrams". It isn't. Critics are right that text diagrams are less expressive than a proper renderer. The point is compatibility. If you need diagrams in a terminal, a debugger, a CLI output, or a README viewer that does not support Mermaid, this approach is practical in a way HTML rendering simply is not.
This version is based on the older, more fully featured Go library and compiled to WebAssembly for in-browser use. The standout detail from the source is support for colors, which makes the output much easier to scan than plain monochrome boxes when you want to show state or flow.
What I like is that this keeps the source format in Mermaid. You are not drawing twice, and you are not maintaining a separate ASCII version by hand. That matters if you already document systems as code or generate operational docs alongside AI workflow automation and other engineering artifacts.
The main limitation is obvious: layout fidelity will never match native Mermaid rendering. So I would treat this as a fallback format, not the canonical experience. But as a fallback, it is a good one, especially for text-first tooling and developer-facing outputs like custom MCP server development, terminal dashboards, or generated runbooks.
If this is relevant to your stack, read the original post and try the tool. It is a clean example of using WebAssembly to move a useful CLI-style library into the browser without turning it into a bloated app.
