What commenters asked our summary
In our own words. Each line links to the comment it is based on.
- How filesystem and registry access is handled, whether stubbed or virtualised in the browser.From this comment
- Whether speed comes from an interpreted core and how heavier binaries perform.From this comment
- Whether programs could be launched from a URL parameter, such as games or screensavers.From this comment
- Where the executables that users run actually come from.From this comment
What they doubted or pushed back on our summary
- Famous cheats in a bundled game card program do not work apart from two values.From this comment
- Shell library coverage is too thin to run some classic file and text utilities.From this comment
- Double-clicking does not register inside a bundled solitaire-style game.From this comment
- Old executables built with Visual Basic and QuickBASIC fail on missing runtime libraries and odd errors.From this comment
What the maker answered our summary
15 replies from the maker in the thread; the points below are the ones we could tie to a comment.
- The readme, including a line recommending AI coding tools, was itself written by AI.From this comment
- The virtual filesystem and registry live in browser storage, and the CPU is emulated in TypeScript without JIT.From this comment
- Speed comes from native JavaScript API calls, since the CPU emulation is slower than JIT-based approaches.From this comment
- A basic text editor now launches as a simple text area, but filesystem work is still incomplete.From this comment
What a builder can take from it: Commenters warmly received the demo but kept testing specific programs, so a builder should expect gaps in compatibility and answer them with concrete progress. our reading
The title, taken apart our calculation
This post got 195 points; the median for all 1442 posts is 112.
When it was posted our calculation
Friday at 13:00 UTC. Of 3,788 Show HN posts submitted in that UTC hour over the window (2025-11-20 to 2026-11-20), 112 (3%) 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