What commenters asked our summary
In our own words. Each line links to the comment it is based on.
- How does the tool locate headers and build instructions for included libraries, and is there a standard layout?From this comment
- How does it handle dependency graphs where two libraries need conflicting versions of one shared library?From this comment
- Can it use system-wide libraries that normally need the operating system package manager?From this comment
- What does this offer that an established dependency manager does not?From this comment
- Will there be a file-watching rebuild command like the one in another ecosystem?From this comment
What they doubted or pushed back on our summary
- Wrapping or generating another build system is the wrong layer; that system should be replaced outright.From this comment
- Installing by piping a script into a shell and editing the shell startup file seems untrustworthy.From this comment
- Depending on that generator tool is a problem, especially for embedded targets where it is overkill.From this comment
- Handling all the odd platform and legacy cases is what separates a usable tool from a demo.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.
- System-wide dependencies are planned but not there yet.From this comment
- It generates starter projects and editable files, manages builds, and saves reusable templates.From this comment
- Since most existing projects already use that generator, building on it lets the tool focus on making hard tasks simpler.From this comment
- A watch command is planned, and the tool is free open source, unlike paying for an assistant.From this comment
What a builder can take from it: Expect users to judge a new build tool mainly on dependency discovery, offline use, and how far it commits to replacing existing tooling rather than wrapping it. our reading
The title, taken apart our calculation
This post got 177 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
Thursday at 16:00 UTC. Of 3,565 Show HN posts submitted in that UTC hour over the window (2025-11-20 to 2026-11-20), 146 (4.1%) reached 50 points; on Thursdays it was 2.7% of 8,077. 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