Edition of Wednesday 11 November 2026

Go Turns 17

Comments on “Go Turns 17”

Claim-checked. Scored by all three judges, and its checkable claims were compared with the sources it cites. How far stories are checked

The Go team's anniversary review covers Go 1.26 and 1.27. Go 1.27 makes encoding/json/v2 generally available, with up to 10× faster unmarshaling, and adds generic methods. Its HTTP/1 transport now drains small unread bodies, giving up to a 5× speedup for sequential requests, and small allocations run up to 30% faster. Green Tea became the default collector in 1.26; the 10–40% overhead reduction and the goroutine leak profiler's false-positive claims were not verified. A first URGENT release answered the eMudhra weak-key incident within 7.5 hours.

Read the original at go.dev. The judges saw only its text, with the site, the author and link domains removed; they are shown again after ranking.

Why it ranked

No. 10 of 143 with a score of 0.70. The panel rated it highest on practical relevance (0.83) and reader interest (0.82), lowest on significance (0.69). Placed No. 10, No. 16 by score alone: the placement terms moved other stories past it.

AI judgeJudge 2claude-haiku-5-5
Annual Go language roundup with substantial technical detail on generics, JSON v2, GC, and security response; largely a release summary, with some promotional framing and ecosystem-wide relevance.
AI judgeJudge 3gpt-5.6-luna
A substantive anniversary and roadmap covering major Go language, library, runtime, security, performance, and tooling changes. It is somewhat promotional and includes forward-looking claims, but provides extensive concrete technical detail and actionable upgrade context.

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.70total under rubric v2.3

Judges’ mean answer per question, on a scale from 0 to 1. Questions marked minus count against the score.
  • Significance0.69
  • Reader interest0.82
  • Audience breadth0.76
  • Practical relevance0.83
  • Substantiated0.74
  • Technical depth0.79
  • New information0.82
  • Counts against: Promotional0.26
  • Counts against: Overclaim0.26

Each judge’s answer per question (0–1), their mean and spread, and what the question adds to the score (weight × mean).

QuestionJudge 1Judge 2Judge 3MeanSpreadWeightContribution (weight times mean)
SignificanceHow much does this change what people in tech know or can do?0.750.500.820.690.32+0.24+0.166
Reader interestWould a well-informed senior engineer or tech founder want to read this today, and likely pass it on?0.750.800.920.820.17+0.26+0.214
Audience breadthHow many people who build technology does it concern?0.650.750.880.760.23+0.13+0.099
Practical relevanceHow useful is it to someone who builds software or tech products?0.910.700.900.830.20+0.22+0.184
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.780.600.840.740.24+0.05+0.037
Technical depthHow technically substantive is it?0.800.700.880.790.18+0.05+0.040
New informationDoes it contain information absent from the stories covered in the last 7 days (list provided)?0.870.600.980.820.38+0.05+0.041
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.100.250.420.260.32−0.19−0.049
OverclaimDo the headline or conclusions claim more than the body supports?0.140.350.300.260.21−0.11−0.029
Sum of contributions+0.702
Claim-check penalty0.000
Total, as published0.702

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.

Ranked #10 on Rubric, 11 Nov 2026
<a href="https://rubric.hrih.si/editions/2026-11-11/10/"><img src="https://rubric.hrih.si/badge/2026-11-11/10.svg" alt="Ranked #10 on Rubric, 11 Nov 2026" width="245" height="28"></a>

Claim check

Claim check: 6 matches source · 2 couldn’t check. Each claim is compared with the source the article itself cites; a flag is published only when both checkers agree.

  1. Matches sourceBenchmark result

    encoding/json/v2 and encoding/json/jsontext reached general availability in Go 1.27 and deliver up to 10× faster unmarshaling.

    The cited source says the same thing.

    The article says

    “this modern JSON API brings safer, stricter defaults, flexible caller- and type-specified customization, and up to 10× faster unmarshaling”

    The source says

    “The Unmarshal performance of v2 is significantly faster than v1, with benchmarks demonstrating improvements of up to 10x”

    Source cited by the article: go.dev/blog/jsonv2

  2. Matches sourceNumber

    Go 1.27's HTTP transport automatically drains small unread response bodies in the background on close, giving up to a 5× speedup for sequential HTTP/1 requests.

    The cited source says the same thing.

    The article says

    “turning a widespread latency footgun into up to a 5× speedup for sequential HTTP/1 requests”

    The source says

    “calling this function 100 times against index.golang.org takes ~710 milliseconds on Go 1.26 on my machine. On Go 1.27, the same program takes ~150 milliseconds”

    Source cited by the article: go.dev/blog/http-connection-reuse

  3. Couldn’t checkBenchmark result

    The Green Tea garbage collector became the default in Go 1.26 and reduces garbage collection overhead by 10–40% in real-world workloads, with an additional ~10% on recent amd64 processors using AVX-512.

    The source was unreachable, paywalled or too long, or the two checkers disagreed.

    The article says

    “reduce garbage collection overhead by 10–40% in real-world workloads—and by an additional ~10% on recent amd64 processors using AVX-512 vector instructions during scanning”

    The source says

    No passage could be compared.

    Source cited by the article: go.dev/blog/greenteagc

  4. Matches sourceNumber

    Go 1.27's size-specialized memory allocation, with fast-path routines for size classes up to 80 bytes, made small allocations up to 30% faster.

    The cited source says the same thing.

    The article says

    “Generating dedicated fast-path allocator routines for size classes up to 80 bytes made small allocations up to 30% faster”

    The source says

    “Allocations can be up to 20-30% faster, making allocation-heavy programs up to 1% faster”

    Source cited by the article: go.dev/blog/size-specialized-allocations

  5. Couldn’t checkNumber

    The goroutine leak profiler identifies leaks in production with near-zero false positives and zero overhead when not in use.

    The source was unreachable, paywalled or too long, or the two checkers disagreed.

    The article says

    “pinpoint leaks in production with near-zero false positives and zero overhead when not in use”

    The source says

    No passage could be compared.

    Source cited by the article: go.dev/blog/goroutine-leak-profiles

  6. Matches sourceFirst, only or fastest

    The Go Security team shipped a fix within seven and a half hours of initial notification of the eMudhra incident, in its first-ever URGENT track security release (Go 1.27.3 and Go 1.26.10).

    The cited source says the same thing.

    The article says

    “Within seven and a half hours of initial notification, the Go Security team shipped a targeted block in our first-ever URGENT track security release (Go 1.27.3 and Go 1.26.10”

    The source says

    “Within approximately seven and a half hours of being notified, we shipped a targeted patch, which was included in our first-ever URGENT track security release”

    Source cited by the article: go.dev/blog/emudhra-incident

  7. Matches sourceNumber

    In the eMudhra incident, eight intermediate TLS and code-signing certificates chaining to a widely trusted root CA were found to use trivially weak private keys.

    The cited source says the same thing.

    The article says

    “eight intermediate TLS and code-signing certificates chaining to a widely trusted root CA were discovered to use trivially weak private keys”

    The source says

    “On October 17, Mozilla added eight intermediate certificates (six used for TLS, and two used for code signing) issued by a root certificate controlled by eMudhra to OneCRL”

    Source cited by the article: go.dev/blog/emudhra-incident

  8. Matches sourceVersion

    Go 1.27 introduced generic methods on non-interface types.

    The cited source says the same thing.

    The article says

    “Go 1.27 introduced generic methods on non-interface types”

    The source says

    “Go 1.27 takes a different view and consequently adds generic methods to Go”

    Source cited by the article: go.dev/blog/generic-methods

Also covered by

No other coverage was clustered with this story.

Elsewhere

Elsewhere: HN 11 pts, front page

Discussion on Hacker News

Recorded for context only, checked 11 Nov 2026, 05:47 UTC. It played no part in the ranking.

Panel for this edition

Four AI agents ranked this edition: three judges scored every story blind to its site and author, and a fourth compared the top stories’ claims with the sources they cite. Summaries are written by AI.

Model versions are pinned for every edition. How ranking works describes rubric v2.3.

Comments

Readers’ comments on this story have a page of their own, ranked by a public rubric rather than by votes.

Comments on “Go Turns 17”

More on Rubric

From the last 7 editions, chosen by shared topic, score and date.