What commenters asked our summary
In our own words. Each line links to the comment it is based on.
- Whether the layout resolver performs edge routing, or if it only supports simple from/to connectionsFrom this comment
- Whether conflicting placement statements cause an error or the first declaration silently winsFrom this comment
- Whether the tool could output only absolute positions as JSON so other renderers can be targetedFrom this comment
- Why build a new language rather than adding placement constraints directly to an existing open-source diagram toolFrom this comment
- How capable and convenient the syntax actually is once read more carefullyFrom this comment
What they doubted or pushed back on our summary
- One user found the tool buggy: a curved arrow was not produced when connecting two nodesFrom this comment
- A commenter disliked the dependency footprint and would prefer an implementation requiring fewer dependenciesFrom this comment
- Placement control is probably unnecessary for fixed-layout diagrams and only matters for flowchartsFrom this comment
- Some users want the full depth of a mature drawing library rather than a narrower diagram toolFrom this comment
What the maker answered our summary
47 replies from the maker in the thread; the points below are the ones we could tie to a comment.
- The tool lacks obstacle-aware auto-routing, though multiple edges to one side share space and bow apartFrom this comment
- Custom themes are not yet available and will be made a priorityFrom this comment
- Layout instructions do become absolute positions; a CLI option to emit them as JSON is plannedFrom this comment
- The scope is deliberately narrow: boxes, groups and arrows with relative placement, not full generalityFrom this comment
What a builder can take from it: Builders should listen closely to commenters' workflow pain points, answer specific technical questions plainly, and accept small bug reports quickly to build trust. our reading
The title, taken apart our calculation
This post got 415 points; the median for all 1442 posts is 112. In Open source projects (328 posts) the median is 103 points and 38 comments.
When it was posted our calculation
Saturday at 17:00 UTC. Of 3,019 Show HN posts submitted in that UTC hour over the window (2025-11-20 to 2026-11-20), 109 (3.6%) reached 50 points; on Saturdays it was 3% of 4,953. The average over all hours is 2.9%. One post's time does not explain its result; the full table of hours is on the Show HN hub.
Check your title our calculation
Type the title you plan to post. It is compared with 1,442 Show HN posts that reached 50 or more points: its length, its shape, and how posts of that length and shape did. Nothing is sent anywhere.
Type a title above to see where it sits.
Draft my Show HN post
Paste your site address and get title options and a first comment for your own Show HN post, written from what your site says and checked against the numbers above. Nothing is posted for you.
Free to try and no account needed. FoxPlug is for people who ship several projects and keep stalling on telling anyone: it turns what you ship into posts you approve before anything goes out. See what each plan includes.
More Open source projects teardowns
Points, comments, titles and times are Hacker News's own numbers, read from the post itself, last updated Nov 2026. Summaries of what people said are ours, written in our own words, and each one links to the comment it came from. Percentages and medians marked "our calculation" are computed from the posts counted on the page: they describe what happened, not what will happen to your post. FoxPlug posts nothing for you. Plans and limits are on the pricing page. Questions: support.
After the launch post: a changelog your users read
A launch brings visitors once. FoxPlug turns what you ship afterwards into a public changelog and ready posts, so the next visitor finds something new.
Start your changelog See a SaaS changelog example
Free to start. Pro is a month.
FoxPlug Pro
- A public changelog page and feed for each project
- Visual cards and walkthrough videos made from what you shipped
- Posts for X, LinkedIn and dev.to written from your changes
- Connect GitHub and the tools you build with