Haybarn 2.0: DuckDB 2.0 with a much faster start in the browser
Comments on “Haybarn 2.0: DuckDB 2.0 with a much faster start in the browser”
Claim-checked. Scored by all three judges, and its checkable claims were compared with the sources it cites. How far stories are checked
Query.Farm released Haybarn 2.0, its distribution of DuckDB 2.0.0 with signed extensions, HTTP/2 remote reads and bug fixes across the engine and clients. Its headline result is WebAssembly startup: loading five extensions single-threaded took 0.87 s with prefetch, against 3.42 s for DuckDB-Wasm, which it says cannot load extensions in its multithreaded build. These are vendor medians from one Apple M3, and the shell and Python timings could not be checked. Extension coverage differs from DuckDB's, and Haybarn is still a release candidate.
Why it ranked
No. 20 of 109 with a score of 0.64. The panel rated it highest on new information (0.92) and technical depth (0.91), lowest on audience breadth (0.50). Placed No. 20, No. 44 by score alone: the placement terms moved other stories past it.
- AI judgeJudge 2claude-haiku-5-5
- Substantive technical release of a DuckDB distribution with detailed, reproducible fixes and benchmarks; a data-tooling release of moderate breadth, with some self-promotional framing.
- AI judgeJudge 3gpt-5.6-luna
- A highly technical DuckDB distribution release with reproducible benchmarks, implementation details, compatibility notes, security fixes, and actionable usage guidance. Broadly useful to data and developer-tool builders, though narrower than ecosystem-wide infrastructure news.
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.54
- Reader interest0.73
- Audience breadth0.50
- Practical relevance0.77
- Substantiated0.89
- Technical depth0.91
- New information0.92
- Counts against: Promotional0.17
- Counts against: Overclaim0.21
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.56 | 0.35 | 0.72 | 0.54 | 0.37 | +0.24 | +0.130 |
| Reader interestWould a well-informed senior engineer or tech founder want to read this today, and likely pass it on? | 0.69 | 0.60 | 0.90 | 0.73 | 0.30 | +0.26 | +0.190 |
| Audience breadthHow many people who build technology does it concern? | 0.51 | 0.40 | 0.58 | 0.50 | 0.18 | +0.13 | +0.065 |
| Practical relevanceHow useful is it to someone who builds software or tech products? | 0.87 | 0.60 | 0.83 | 0.77 | 0.27 | +0.22 | +0.169 |
| 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.97 | 0.75 | 0.94 | 0.89 | 0.22 | +0.05 | +0.044 |
| Technical depthHow technically substantive is it? | 0.99 | 0.80 | 0.94 | 0.91 | 0.20 | +0.05 | +0.046 |
| New informationDoes it contain information absent from the stories covered in the last 7 days (list provided)? | 0.88 | 0.90 | 0.98 | 0.92 | 0.10 | +0.05 | +0.046 |
| 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.07 | 0.35 | 0.08 | 0.17 | 0.28 | −0.19 | −0.032 |
| OverclaimDo the headline or conclusions claim more than the body supports? | 0.28 | 0.30 | 0.04 | 0.21 | 0.26 | −0.11 | −0.023 |
| Sum of contributions | +0.635 | ||||||
| Claim-check penalty | 0.000 | ||||||
| Total, as published | 0.635 | ||||||
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-06/20/"><img src="https://rubric.hrih.si/badge/2026-11-06/20.svg" alt="Ranked #20 on Rubric, 6 Nov 2026" width="238" height="28"></a>Claim check
Claim check: 3 matches source · 3 no source given · 2 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 givenVersion
Haybarn 2.0 is built on DuckDB 2.0.0 across the CLI, libraries, extensions and the Python, Node, Rust, Go, JDBC, ODBC and WebAssembly clients.
The article gives no link or citation for it.
The article says “Haybarn 2.0 moves all of that to DuckDB 2.0.0, across the CLI, libraries, extensions and the Python, Node, Rust, Go, JDBC, ODBC and WebAssembly clients”
The source says No source to compare with.
Matches sourceNumber
With 48 threads and 48 connections, throughput rose 13 to 15% after the fix that makes the result-collecting thread wait instead of spinning, while ORDER BY of 20 million rows at 48 threads got about 10% slower in median wall time.
The cited source says the same thing.
The article says “With 48 threads and 48 connections, throughput rose 13 to 15%. The tradeoff: ORDER BY of 20 million rows at 48 threads got about 10% slower in median wall time”
The source says “48 threads × 48 connections: throughput | 1762 qps | 2027 qps (+15%), with 14% less CPU”
Source cited by the article: github.com/duckdb/duckdb/pull/27738
Matches sourceCausal conclusion
Since late October, GitHub's release downloads send a 9.2 KB content-security-policy header line, which made reading a Parquet file from a GitHub release fail on the httplib backend.
The cited source says the same thing.
The article says “Since late October, GitHub’s release downloads send a 9.2 KB content-security-policy line, so reading a Parquet file from a GitHub release failed on the httplib backend”
The source says “the 302 it answers with now carries a `content-security-policy` header of over 9 KiB on one line”
Source cited by the article: github.com/duckdb/duckdb/pull/27825
No source givenFirst, only or fastest
DuckDB-Wasm's multithreaded build cannot load extensions at all, while the same LOADs work on its single-threaded build and on Haybarn-Wasm's multithreaded build.
The article gives no link or citation for it.
The article says “DuckDB-Wasm’s multithreaded build can’t load extensions at all”
The source says No source to compare with.
No source givenBenchmark result
With five extensions loaded single-threaded, DuckDB-Wasm took 3.42 s, Haybarn-Wasm 2.19 s, and Haybarn-Wasm with prefetch 0.87 s.
The article gives no link or citation for it.
The article says “DuckDB-Wasm 3.42 s”
The source says No source to compare with.
Couldn’t checkNumber
The Haybarn shell's time to the prompt went from 2.25 to 1.38 seconds on the threaded build in Chromium, and from 1.82 to 1.16 on the single-threaded build, after it started using prefetch in rc12.
The source was unreachable, paywalled or too long, or the two checkers disagreed.
The article says “its time to the prompt went from 2.25 to 1.38 seconds on the threaded build in Chromium, and from 1.82 to 1.16 on the single-threaded build”
The source says No passage could be compared.
Source cited by the article: shell.haybarn.query.farm
Couldn’t checkNumber
In Haybarn's stress test, Python 3.14 exit failures per 300 runs went from 13 and 39 to none on the two affected cases.
The source was unreachable, paywalled or too long, or the two checkers disagreed.
The article says “failures per 300 runs went from 13 and 39 to none on the two affected cases”
The source says No passage could be compared.
Source cited by the article: github.com/duckdb/duckdb-python/pull/719
Matches sourceDate
DuckDB's release calendar has the 2.0.1 merge freeze on November 11 and the release on November 18.
The cited source says the same thing.
The article says “DuckDB’s release calendar has the 2.0.1 merge freeze on November 11 and the release on November 18”
The source says “2026-11-11 | Merge freeze 2.0.1 | | 2026-11-18 | Release 2.0.1”
Source cited by the article: duckdb.org/release_calendar
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 6 Nov 2026, 05:47 UTC. It played no part in the ranking.