What commenters asked our summary
In our own words. Each line links to the comment it is based on.
- How does static recompilation handle timing-sensitive PS2 hardware like vector units without cycle-accurate emulation?From this comment
- Could the recompiler itself be compiled to WebAssembly so conversion runs in a browser?From this comment
- Would it run on Steam Deck?From this comment
- Can it support old low-end graphics cards?From this comment
- What is performance like on heavier titles?From this comment
What they doubted or pushed back on our summary
- It still emulates a core system component rather than fully recompiling everything.From this comment
- Many recomp projects may bypass the trust and vetting of the established emulator scene, raising malware concerns.From this comment
- Hosting such a build publicly would effectively mean distributing games for free, which raises legal issues.From this comment
- Easy recompilation enabled by AI could reduce studios' incentive to invest in original games if they can be copied freely.From this comment
What the maker answered our summary
7 replies from the maker in the thread; the points below are the ones we could tie to a comment.
- It is not cycle-accurate; blocks deduct instruction counts from a cycle budget, with interrupts and DMA delivered at block boundaries.From this comment
- A native Linux build exists that can run on Deck, though the native host is single-threaded and browser build may work in desktop mode.From this comment
- The IOP is interpreted but only runs game-shipped driver modules, consuming about two percent of CPU time in one test.From this comment
- The recompiler is cross-platform C++; generating WebAssembly directly avoids needing a browser-hosted compiler.From this comment
What a builder can take from it: Static recompilation projects should clearly state what is recompiled versus emulated, address legal and trust concerns, and confirm performance on real hardware cases. our reading
The title, taken apart our calculation
This post got 316 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
Monday at 06:00 UTC. Of 1,105 Show HN posts submitted in that UTC hour over the window (2025-11-20 to 2026-11-20), 25 (2.3%) reached 50 points; on Mondays it was 3.1% of 7,396. 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