What commenters asked our summary
In our own words. Each line links to the comment it is based on.
- Will compile errors show clear messages pointing to the original Lisp code?From this comment
- Can the standard Rust language server provide IDE features for this syntax?From this comment
- How does the syntax handle breaking changes while staying compatible with Rust?From this comment
- Is there a tool that does the reverse, converting uglier syntax into Rust?From this comment
- Is anyone building something similar that compiles to Go?From this comment
What they doubted or pushed back on our summary
- It is just Rust written in s-expressions, not a real Lisp dialect compiling to Rust.From this comment
- No examples cover lifetimes or turbofish, despite claiming complete syntax support.From this comment
- S-expression parentheses are hard for coding agents, making the syntax a poor choice.From this comment
- The code currently does not compile due to stray span code and a formatting trait error.From this comment
What the maker answered our summary
5 replies from the maker in the thread; the points below are the ones we could tie to a comment.
- A direct Rust escape macro is available for anything not yet implemented.From this comment
- The project was built using a specific language model and coding tool.From this comment
- The maker finds a similar ownership-focused Lisp cool and admits taking the laziest path.From this comment
- Error messages and spans are being added following a suggestion.From this comment
What a builder can take from it: Builders should test and fix their code before launch, provide examples for tricky syntax, and be ready to address feedback on tooling and error reporting. our reading
The title, taken apart our calculation
This post got 218 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
Saturday at 21:00 UTC. Of 1,956 Show HN posts submitted in that UTC hour over the window (2025-11-20 to 2026-11-20), 55 (2.8%) reached 50 points; on Saturdays it was 3% of 4,953. 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