What commenters asked our summary
In our own words. Each line links to the comment it is based on.
- Whether the name abbreviates Turbo Rust and if it should be stated in the readme given trademark risk.From this comment
- Whether DOS builds exist and if it performs well enough on hardware from the nineties.From this comment
- How to build a standalone Rust file, since it errors without a project manifest.From this comment
- Whether any editor offering this look also provides full vim-style editing support.From this comment
- Whether the library's object model allows deriving and extending built-in classes for custom controls and windows.From this comment
What they doubted or pushed back on our summary
- Rust compile times remain slow compared with old fast compilers, undermining the retro promise.From this comment
- The debugger, central to the experience, is listed as not implemented.From this comment
- The screenshots show modern window chrome with rounded corners that looks broken.From this comment
- Recalling Turbo C from school days in 2015, this style felt unpleasant to work with.From this comment
What the maker answered our summary
34 replies from the maker in the thread; the points below are the ones we could tie to a comment.
- Refuses to confirm what the T means, noting some related trademarks are current and renewed.From this comment
- Calls the project more an art piece than a developer tool and promises to look into the debugger.From this comment
- Accepts the screenshot critique and may redo them.From this comment
- Agrees to document that a project must be created first.From this comment
What a builder can take from it: A nostalgic look can attract attention, but builders should expect scrutiny of core gaps like debugging, speed and setup. our reading
The title, taken apart our calculation
This post got 178 points; the median for all 1442 posts is 112. In Developer tools (185 posts) the median is 106 points and 38 comments.
When it was posted our calculation
Thursday at 05:00 UTC. Of 1,043 Show HN posts submitted in that UTC hour over the window (2025-11-20 to 2026-11-20), 29 (2.8%) 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 Developer tools 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