What's new in the .NET 11 runtime
Comments on “What's new in the .NET 11 runtime”
Claim-checked. Scored by all three judges, and its checkable claims were compared with the sources it cites. How far stories are checked
Microsoft's .NET 11 release candidate notes say the runtime raises its minimum hardware baseline on x86/x64 to x86-64-v2 and on Arm64 to require LSE on Windows, dropping support for older CPUs.
Why it ranked
No. 57 of 143 with a score of 0.64. The panel rated it highest on new information (0.95) and technical depth (0.90), lowest on significance (0.68). The claim check took 0.100 off. Placed No. 57, No. 49 by score alone: the eighth 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
- Official .NET 11 runtime release notes with detailed, specific technical changes (async, JIT, hardware requirements) affecting many .NET builders; primary source, release-type content, little overlap with recent stories.
- AI judgeJudge 3gpt-5.6-luna
- A detailed, technically substantive .NET 11 runtime release overview covering async, JIT, AOT, WebAssembly, SIMD, hardware baselines, diagnostics, and reliability. It is broadly useful to .NET builders, though primarily relevant to that ecosystem.
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.64total under rubric v2.3
- Significance0.68
- Reader interest0.75
- Audience breadth0.69
- Practical relevance0.82
- Substantiated0.79
- Technical depth0.90
- New information0.95
- Counts against: Promotional0.04
- Counts against: Overclaim0.12
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.72 | 0.60 | 0.72 | 0.68 | 0.12 | +0.24 | +0.163 |
| Reader interestWould a well-informed senior engineer or tech founder want to read this today, and likely pass it on? | 0.60 | 0.80 | 0.86 | 0.75 | 0.26 | +0.26 | +0.196 |
| Audience breadthHow many people who build technology does it concern? | 0.66 | 0.80 | 0.62 | 0.69 | 0.18 | +0.13 | +0.090 |
| Practical relevanceHow useful is it to someone who builds software or tech products? | 0.89 | 0.75 | 0.82 | 0.82 | 0.14 | +0.22 | +0.181 |
| 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.76 | 0.70 | 0.90 | 0.79 | 0.20 | +0.05 | +0.039 |
| Technical depthHow technically substantive is it? | 0.95 | 0.85 | 0.90 | 0.90 | 0.10 | +0.05 | +0.045 |
| New informationDoes it contain information absent from the stories covered in the last 7 days (list provided)? | 0.92 | 0.95 | 0.98 | 0.95 | 0.06 | +0.05 | +0.048 |
| 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.05 | 0.03 | 0.03 | 0.04 | 0.02 | −0.19 | −0.007 |
| OverclaimDo the headline or conclusions claim more than the body supports? | 0.12 | 0.15 | 0.08 | 0.12 | 0.07 | −0.11 | −0.013 |
| Sum of contributions | +0.742 | ||||||
| Claim-check penalty | −0.100 | ||||||
| Total, as published | 0.642 | ||||||
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-11/57/"><img src="https://rubric.hrih.si/badge/2026-11-11/57.svg" alt="Ranked #57 on Rubric, 11 Nov 2026" width="245" height="28"></a>Claim check
Claim check: 2 matches source · 1 not in source · 4 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.
Couldn’t checkGeneralization
For Windows on Arm64, .NET 11 requires the LSE instruction set, which Windows 11 and all Arm64 CPUs officially supported by Windows 10 already require.
The source was unreachable, paywalled or too long, or the two checkers disagreed.
The article says “This is required by Windows 11 and by all Arm64 CPUs officially supported by Windows 10”
The source says No passage could be compared.
Source cited by the article: learn.microsoft.com/en-us/windows-hardware/design/minimum/minimum-hardware-requirements-overview
Matches sourceVersion
.NET 11 raises the x86/x64 baseline from x86-64-v1 to x86-64-v2 on all three operating systems.
The cited source says the same thing.
The article says “the baseline is updated from x86-64-v1 to x86-64-v2”
The source says “For all three operating systems (Apple, Linux, and Windows), the baseline is updated from x86-64-v1 to x86-64-v2”
Source cited by the article: learn.microsoft.com/en-us/dotnet/core/compatibility/jit/11/minimum-hardware-requirements
Matches sourceVersion
The ReadyToRun target for Windows and Linux on x86/x64 has been updated to x86-64-v3.
The cited source says the same thing.
The article says “The ReadyToRun target has been updated to x86-64-v3 for Windows and Linux”
The source says “The ReadyToRun target has been updated to x86-64-v3 for Windows and Linux, while it remains unchanged for Apple”
Source cited by the article: learn.microsoft.com/en-us/dotnet/core/compatibility/jit/11/minimum-hardware-requirements
No source givenVersion
The .NET 11 runtime libraries are compiled with runtime-async=on and no longer contain compiler-generated state machines.
The article gives no link or citation for it.
The article says “The .NET runtime libraries themselves are compiled with runtime-async=on. The runtime libraries no longer contain compiler-generated state machines and rely entirely on runtime-provided async”
The source says No source to compare with.
No source givenBenchmark result
Specializing Comparer<T>.Default and EqualityComparer<T>.Default in ReadyToRun images yields up to a 20× improvement for collections operations relying on the default comparer.
The article gives no link or citation for it.
The article says “benchmarks show up to a 20× improvement for collections operations that rely on the default comparer”
The source says No source to compare with.
No source givenBenchmark result
Cached interface dispatch yields up to 200x improvements in interface-heavy code on platforms without JIT support such as iOS.
The article gives no link or citation for it.
The article says “Cached dispatch yields up to 200x improvements in interface-heavy code on these targets”
The source says No source to compare with.
Not in sourceNumber
Guid.NewGuid() on Linux now uses the getrandom() syscall with batch caching, yielding approximately 12% throughput improvement.
The cited source does not contain it.
The article says “yielding approximately 12% throughput improvement for GUID generation”
The source says “On non-Windows platforms, starting with .NET 6, this function calls the OS's underlying cryptographically secure pseudo-random number generator (CSPRNG) to generate 122 bits of strong entropy”
Source cited by the article: learn.microsoft.com/en-us/dotnet/api/system.guid.newguid
No source givenNumber
Arm64 versions of Vector*.Count, IndexOf, and LastIndexOf no longer route through ExtractMostSignificantBits, yielding a 5–50% improvement in workloads using these APIs.
The article gives no link or citation for it.
The article says “yielding a 5–50% improvement in workloads that use these APIs in their core loop”
The source says No source to compare with.
Also covered by
No other coverage was clustered with this story.
Elsewhere
Elsewhere: HN 250 pts, front page
Recorded for context only, checked 11 Nov 2026, 05:47 UTC. It played no part in the ranking.