Monosketch

Original Article ↗ Hacker News Discussion ↗

Overall reception

  • Many commenters find Monosketch “really cool,” simple, and immediately useful; several say it’s better/easier than Asciiflow, draw.io, or Excalidraw for text diagrams.
  • Others are more jaded, framing it as “another ASCII box tool” or a minor iteration on long‑existing ideas.

Comparison with existing tools

  • Monodraw is repeatedly cited as the benchmark native tool; users praise it as one of their best purchases but note it is Mac‑only and non‑FOSS, so Monosketch is welcomed as an open, cross‑platform alternative.
  • Several web and CLI alternatives are listed (Asciiflow, textpaint, textik, cascii, svgbob, Graph‑Easy, Markdeep, Emacs packages, etc.), positioning Monosketch within a rich ecosystem.
  • Some see it as especially promising for people who left macOS and miss Monodraw.

Features, UX, and requests

  • Praised: sticky connector lines, easy export as text, clear mental model for ASCII diagrams.
  • Pain points and wishes:
    • Making lines “stick” and moving small rectangles is finicky.
    • Copy defaults to JSON; multiple users want plain text/ASCII on Ctrl/Cmd‑C and JSON as a secondary/export option.
    • Export/“copy as text” should be more discoverable, with a visible button.
    • Desire for tool hotkeys (e.g., 1–5 like Excalidraw) and a mode to lock the current tool for rapid drawing.
    • Multiple independent canvases per browser tab/session and disabled spellcheck for diagram labels are requested.
    • Some ask about support for polygons and smarter sticky lines; current character/grid constraints make true arbitrary polygons hard.

“ASCII” terminology and accessibility

  • Several pedantic but substantive notes: the tool uses Unicode box‑drawing and symbols, not pure 7‑bit ASCII; people discuss “extended ASCII,” DOS code pages, and Unicode history.
  • Accessibility concerns: complex ASCII/Unicode diagrams are hard for screen readers and can be an “accessibility nightmare.” Others argue creative freedom shouldn’t be limited, or speculate that modern LLMs might mitigate this by interpreting diagrams.

Use cases, LLMs, and purpose today

  • Debated purpose in 2020s: proponents value diagrams that live in source code, work in terminals, diff well under git, and are LLM‑friendly.
  • Some highlight “ASCII‑driven development,” mermaid diagrams, and agent workflows; others see heavy ASCII usage as a fad or a symptom of programming being “stuck in the 1970s.”
  • There’s meta‑discussion about AI generating and editing such diagrams, anthropomorphizing models, and the risk of AI‑produced but technically incorrect diagrams misleading novices.