Go source to running container in 3.8 seconds
Comments on “Go source to running container in 3.8 seconds”
Claim-checked. Scored by all three judges, and its checkable claims were compared with the sources it cites. How far stories are checked
A developer describes getting from saved Go source to a running production container in 3.8 seconds, by combining a warm Go build cache with a single shared distroless image into which each new binary is mounted, rather than building and pushing an image per version.
Why it ranked
No. 21 of 62 with a score of 0.65. The panel rated it highest on new information (0.91) and technical depth (0.90), lowest on significance (0.45).
Every answer behind this is in the table under Score.
Score
0.65total under rubric v2.2
- Significance0.45
- Reader interest0.77
- Audience breadth0.55
- Practical relevance0.80
- Substantiated0.86
- Technical depth0.90
- New information0.91
- Counts against: Promotional0.05
- Counts against: Overclaim0.29
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) |
|---|---|---|---|---|---|---|---|
| Significance | 0.47 | 0.30 | 0.58 | 0.45 | 0.28 | +0.24 | +0.108 |
| Reader interest | 0.74 | 0.72 | 0.86 | 0.77 | 0.14 | +0.26 | +0.201 |
| Audience breadth | 0.59 | 0.45 | 0.62 | 0.55 | 0.17 | +0.13 | +0.072 |
| Practical relevance | 0.88 | 0.70 | 0.82 | 0.80 | 0.18 | +0.22 | +0.176 |
| Substantiated | 0.96 | 0.72 | 0.91 | 0.86 | 0.24 | +0.05 | +0.043 |
| Technical depth | 1.00 | 0.85 | 0.86 | 0.90 | 0.15 | +0.05 | +0.045 |
| New information | 0.90 | 0.90 | 0.94 | 0.91 | 0.04 | +0.05 | +0.046 |
| Promotional | 0.06 | 0.08 | 0.02 | 0.05 | 0.06 | −0.19 | −0.010 |
| Overclaim | 0.35 | 0.35 | 0.18 | 0.29 | 0.17 | −0.11 | −0.032 |
| Sum of contributions | +0.648 | ||||||
| Claim-check penalty | 0.000 | ||||||
| Total, as published | 0.648 | ||||||
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-10-26/21/"><img src="https://rubric.hrih.si/badge/2026-10-26/21.svg" alt="Ranked #21 on Rubric, 26 Oct 2026" width="245" height="28"></a>Claim check
Claim check: 7 no source given · 1 couldn’t check. Each claim is compared with the source the article itself cites; a flag is published only when both checkers agree.
No source givenNumber
Going from a Go source change to a compiled, running production container with a finished first run takes 3.8 seconds using the author's setup.
The article gives no link or citation for it.
The article says “3.8 seconds later it's compiled, running in production on a server and has finished its first run”
The source says No source to compare with.
No source givenBenchmark result
In the author's benchmark, source-by-hash with one shared image took 3.81 s, ko plus registry 5.90 s, and docker build plus registry 6.61 s.
The article gives no link or citation for it.
The article says “Source by hash, one shared image 3.81 s ± 0.15 s”
The source says No source to compare with.
No source givenNumber
A Go rebuild after a one-line edit with a warm cache takes 1.4 s, versus about 20 s for a cold build.
The article gives no link or citation for it.
The article says “A build after a one-line edit takes 1.4 s. A cold one takes about 20 s”
The source says No source to compare with.
No source givenBenchmark result
A cold build took 21.1 s on 6 cores and 19.5 s on 32 CPUs, so core count barely matters.
The article gives no link or citation for it.
The article says “A cold build took 21.1 s on 6 cores and 19.5 s on 32 CPUs”
The source says No source to compare with.
No source givenNumber
Go removes build cache entries unused for at least 5 days, checking at most once a day, with no setting for it.
The article gives no link or citation for it.
The article says “Go removes cache entries unused for at least 5 days, checking at most once a day, and there's no setting for it”
The source says No source to compare with.
Couldn’t checkGeneralization
Temporal's Worker Versioning pins each run to the build it started on, so new runs go to the new build and open runs finish on theirs.
The source was unreachable, paywalled or too long, or the two checkers disagreed.
The article says “Temporal's Worker Versioning pins each run to the build it started on”
The source says No passage could be compared.
Source cited by the article: docs.temporal.io/worker-versioning
No source givenNumber
A friend's CI pipeline went from about 4.7 min to 27 s from push to live, blue/green swap included, after reading a draft.
The article gives no link or citation for it.
The article says “By the end of the day it was 27 s from push to live, blue/green swap included”
The source says No source to compare with.
No source givenCausal conclusion
The same tarball built on the server and in Docker on the desktop gave a byte-identical binary when built with -trimpath.
The article gives no link or citation for it.
The article says “Built with -trimpath, it carries no paths, so the same tarball built on the server and in Docker on my desktop gave the same binary, byte for byte”
The source says No source to compare with.
Also covered by
No other coverage was clustered with this story.
Elsewhere
Elsewhere: HN 1 pts, not on front page
Recorded for context only, checked 26 Oct 2026, 07:27 UTC. It played no part in the ranking.