Three prevailing themes in the discussion
| Theme | What users said | Representative quotes |
|---|---|---|
| 1. Feature set & usability | Participants debated what the tool can actually do (polygons, copy‑to‑text, round‑trip editing) and how it fits into a workflow. | “I just tried all the examples on the home page, it works perfectly.” – simgt “I found cmd+shift+c in the keyboard shortcuts.” – lemontheme “I think it would be possible to maintain an internal model of copied objects, while the clipboard is always filled with usable ASCII?” – TonyStr |
| 2. Positioning vs. other diagramming apps | The tool was compared to Monodraw, Excalidraw, draw.io, and other ASCII‑based editors, with users weighing pros, cons, and price. | “This is really cool. Better than draw.io and excalidraw.” – alexhr “Monodraw got an update the other week. It isn’t being changed, but it doesn’t need to.” – jen729w “Monodraw is in maintenance mode and non‑free. Based on the name, pretty sure that Monosketch is an explicit replacement.” – Apreche |
| 3. Open‑source / licensing & accessibility | Opinions split on the value of a paid, closed‑source product versus a free, FOSS alternative, and on the inherent accessibility problems of ASCII diagrams. | “But it’s not open, and can’t be edited by those who want to. We should always support FOSS.” – orangecoffee “ASCII art is an accessibility nightmare so please don’t use it for docs unless you know what you’re doing and have made it accessible in some other way.” – nasso_dev “ASCII doesn’t contain box‑drawing characters or arrows. I guess it’s a lost cause though…” – Sharlin |
These three themes—feature usability, market positioning, and open‑source/accessibility concerns—capture the bulk of the conversation.