How //go:embed Works: From Source Files to Binary
Comments on “How //go:embed Works: From Source Files to Binary”
3 judges. Scored by all three judges. Only the day’s top stories get the claim check. How far stories are checked
A walkthrough of Go's //go:embed directive, which since Go 1.16 lets programs bake strings, byte slices, or a read-only file system into the compiled binary at build time.
Why it ranked
No. 104 of 139 with a score of 0.59. The panel rated it highest on new information (0.93) and technical depth (0.90), lowest on significance (0.40). Placed No. 104, No. 97 by score alone: the 20th Programming & dev tools story of the day (−0.080). The placement terms move stories; they are not part of the score.
- AI judgeJudge 2claude-haiku-5-5
- Deep, accurate tutorial on Go's embed feature with source-level detail from the compiler and linker; useful to Go builders, though a niche topic with modest significance.
- AI judgeJudge 3gpt-5.6-luna
- A detailed, source-linked explanation of Go’s //go:embed pipeline, runtime behavior, memory implications, testing, and deployment tradeoffs. It is highly actionable for Go developers, though niche and somewhat tutorial-like rather than field-changing.
Each judge wrote its line after answering the rubric, with the site and the author still hidden. Every answer behind this is in the table under Score.
Score
0.59total under rubric v2.3
- Significance0.40
- Reader interest0.64
- Audience breadth0.44
- Practical relevance0.72
- Substantiated0.83
- Technical depth0.90
- New information0.93
- Counts against: Promotional0.04
- Counts against: Overclaim0.17
Each judge’s answer per question (0–1), their mean and spread, and what the question adds to the score (weight × mean).
| Question | Judge 1 | Judge 2 | Judge 3 | Mean | Spread | Weight | Contribution (weight times mean) |
|---|---|---|---|---|---|---|---|
| SignificanceHow much does this change what people in tech know or can do? | 0.49 | 0.30 | 0.40 | 0.40 | 0.19 | +0.24 | +0.095 |
| Reader interestWould a well-informed senior engineer or tech founder want to read this today, and likely pass it on? | 0.60 | 0.60 | 0.72 | 0.64 | 0.12 | +0.26 | +0.166 |
| Audience breadthHow many people who build technology does it concern? | 0.60 | 0.35 | 0.38 | 0.44 | 0.25 | +0.13 | +0.058 |
| Practical relevanceHow useful is it to someone who builds software or tech products? | 0.93 | 0.55 | 0.70 | 0.72 | 0.38 | +0.22 | +0.160 |
| SubstantiatedHow well is it backed? Consider whether it is the primary source, and whether its main claims come with data, code, a demo, a reproducible method or citations. | 0.93 | 0.75 | 0.82 | 0.83 | 0.18 | +0.05 | +0.042 |
| Technical depthHow technically substantive is it? | 1.00 | 0.85 | 0.86 | 0.90 | 0.15 | +0.05 | +0.045 |
| New informationDoes it contain information absent from the stories covered in the last 7 days (list provided)? | 0.90 | 0.90 | 0.99 | 0.93 | 0.09 | +0.05 | +0.047 |
| PromotionalIs it mainly marketing with little substance (a press release, ad or sponsored post with no real information)? A launch post that carries real news is not promotional. | 0.04 | 0.05 | 0.03 | 0.04 | 0.02 | −0.19 | −0.008 |
| OverclaimDo the headline or conclusions claim more than the body supports? | 0.16 | 0.15 | 0.20 | 0.17 | 0.05 | −0.11 | −0.019 |
| Sum of contributions | +0.586 | ||||||
| Claim-check penalty | 0.000 | ||||||
| Total, as published | 0.586 | ||||||
Spread is the highest minus the lowest judge answer. marks a spread above 0.40: the judges disagree, and the story is marked contested.
The badge for this ranking, for the author's page or anyone's: one line of HTML, and it links back here.
<a href="https://rubric.hrih.si/editions/2026-11-05/104/"><img src="https://rubric.hrih.si/badge/2026-11-05/104.svg" alt="Ranked #104 on Rubric, 5 Nov 2026" width="245" height="28"></a>Also covered by
No other coverage was clustered with this story.
Elsewhere
Elsewhere: HN —
Recorded for context only, checked 5 Nov 2026, 05:46 UTC. It played no part in the ranking.