What commenters asked our summary
In our own words. Each line links to the comment it is based on.
- Whether the book covers Clojure, since it seemed missing from the index.From this comment
- Whether the author interviewed a key figure for the chapter on that dialect.From this comment
- Whether a representative middle chapter sample could be shown, not just front matter.From this comment
- What the physical print quality is like when ordered through online stores.From this comment
- Whether earlier, more mathematical language research and formalism were addressed.From this comment
What they doubted or pushed back on our summary
- The cover design looks unpolished and could benefit from professional graphic design help.From this comment
- The sample did not help the buying decision, and an important early history paper was not cited.From this comment
- The bibliography lacks thoroughness on early language history and a programming-language-theory viewpoint.From this comment
- A sample chapter contains a misspelled name and an imprecise claim about tail recursion origins.From this comment
What the maker answered our summary
38 replies from the maker in the thread; the points below are the ones we could tie to a comment.
- A whole chapter covers that dialect, which likely explains its absence from the index.From this comment
- The author did not conduct that interview but would consider adding material in a future edition.From this comment
- A middle chapter sample was posted to better show the book's technical depth.From this comment
- The bibliography was deliberately short under a publisher, listing only directly quoted works.From this comment
What a builder can take from it: Show a representative middle chapter as your sample, keep a corrections list, and expect experts to push for deeper references than a general audience needs. our reading
The title, taken apart our calculation
This post got 252 points; the median for all 1442 posts is 112.
When it was posted our calculation
Tuesday at 15:00 UTC. Of 4,000 Show HN posts submitted in that UTC hour over the window (2025-11-20 to 2026-11-20), 133 (3.3%) reached 50 points; on Tuesdays it was 2.8% of 8,995. 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