What commenters asked our summary
In our own words. Each line links to the comment it is based on.
- Which geometry engine powers the tool and which modeling operations does it currently support?From this comment
- How does this differ from an existing JavaScript drawing library, and is an API link available?From this comment
- Where can users find a full list of supported operations, and are revolved sketches or assemblies possible?From this comment
- Is the project accepting code contributions, and if so when?From this comment
- Why does extrude connect implicitly to a sketch instead of being called as a method on an assigned sketch variable?From this comment
What they doubted or pushed back on our summary
- Using indices as references may break in complex models, so stable identifiers or proximity-based picking would be safer.From this comment
- The interactive region extrude hardcodes a picked point, so later sketch changes may break the model.From this comment
- Code-based CAD tools use imperative languages and only support imperative constraints; declarative constraints would be welcome.From this comment
- Established CAD tools rely on geometry engines refined over decades, so this may suit simple maker parts but not industry needs.From this comment
What the maker answered our summary
8 replies from the maker in the thread; the points below are the ones we could tie to a comment.
- It runs on an open-source compiled geometry engine, most operations work though some are basic, and an API is coming.From this comment
- Assemblies are planned but far off due to difficulty; multiple parts can share a scene without actuation.From this comment
- Contributions will open at the first version after design decisions and a roadmap are settled.From this comment
- Topological naming is hard, so this version uses indices plus filters, with region picking as the selection approach.From this comment
What a builder can take from it: Expect questions about the geometry engine, operation coverage, API access and contribution policy early, and be ready to explain how your referential scheme copes with model changes. our reading
The title, taken apart our calculation
This post got 160 points; the median for all 1442 posts is 112.
When it was posted our calculation
Friday at 18:00 UTC. Of 2,649 Show HN posts submitted in that UTC hour over the window (2025-11-20 to 2026-11-20), 84 (3.2%) reached 50 points; on Fridays it was 2.7% of 6,422. 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 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