Edition of Wednesday 18 November 2026

Green Threads for Node.js

Comments on “Green Threads for Node.js”

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

A pull request to Node.js (#67288), written by James Snell, adds an experimental node:green_threads module. Each green thread is a V8 isolate with its own heap, run on a shared pool of up to 8 OS threads, with no Node APIs and per-thread CPU and memory limits. In his own benchmarks on one 88-CPU machine, an instance used 1.4 MB versus 6.2 MB for a worker, with similar CPU-bound speed. Throughput matched a vm pool without a timeout. There is no preemption, debugger, URL or fetch.

Read the original at jasnell.me. 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. 5 of 142 with a score of 0.71. The panel rated it highest on technical depth (0.95) and new information (0.93), lowest on significance (0.62). Placed No. 5, No. 8 by score alone: the placement terms moved other stories past it.

AI judgeJudge 2claude-haiku-5-5
Detailed, benchmarked write-up of an experimental Node.js PR with real technical depth and new information; relevant to builders of multi-tenant and plugin systems, though it is a prototype with limited near-term reach.
AI judgeJudge 3gpt-5.6-luna
Detailed engineering analysis of a potentially important Node.js concurrency primitive, with implementation specifics, API examples, benchmarks, limitations, comparisons, and reproducible build instructions.

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

Judges’ mean answer per question, on a scale from 0 to 1. Questions marked minus count against the score.
  • Significance0.62
  • Reader interest0.81
  • Audience breadth0.64
  • Practical relevance0.71
  • Substantiated0.89
  • Technical depth0.95
  • New information0.93
  • Counts against: Promotional0.05
  • Counts against: Overclaim0.13

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.540.550.780.620.24+0.24+0.150
Reader interestWould a well-informed senior engineer or tech founder want to read this today, and likely pass it on?0.720.800.900.810.18+0.26+0.210
Audience breadthHow many people who build technology does it concern?0.570.600.760.640.19+0.13+0.084
Practical relevanceHow useful is it to someone who builds software or tech products?0.660.600.880.710.28+0.22+0.157
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.940.800.920.890.14+0.05+0.044
Technical depthHow technically substantive is it?0.990.900.970.950.09+0.05+0.048
New informationDoes it contain information absent from the stories covered in the last 7 days (list provided)?0.870.950.980.930.11+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.050.100.010.050.09−0.19−0.010
OverclaimDo the headline or conclusions claim more than the body supports?0.110.200.080.130.12−0.11−0.014
Sum of contributions+0.715
Claim-check penalty0.000
Total, as published0.715

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 #5 on Rubric, 18 Nov 2026
<a href="https://rubric.hrih.si/editions/2026-11-18/5/"><img src="https://rubric.hrih.si/badge/2026-11-18/5.svg" alt="Ranked #5 on Rubric, 18 Nov 2026" width="238" height="28"></a>

Claim check

Claim check: 3 matches source · 5 no source given. Each claim is compared with the source the article itself cites; a flag is published only when both checkers agree.

  1. Matches sourceVersion

    PR #67288 adds an experimental node:green_threads module to Node.js.

    The cited source says the same thing.

    The article says

    “adds an experimental node:green_threads module to Node.js”

    The source says

    “This implements green threads for Node.js”

    Source cited by the article: github.com/nodejs/node/pull/67288

  2. Matches sourceVersion

    Each green thread is its own V8 isolate with its own heap and garbage collector, and all green threads share a process-wide pool of OS threads.

    The cited source says the same thing.

    The article says

    “each green thread is its own V8 isolate, with its own heap and its own garbage collector”

    The source says

    “It has its own V8 isolate with no Node.js APIs. They run on a small pool of physical threads that they share”

    Source cited by the article: github.com/nodejs/node/pull/67288

  3. Matches sourceNumber

    The green thread pool has as many threads as os.availableParallelism(), up to 8 by default, or as set by NODE_GREEN_THREADS_POOL_SIZE.

    The cited source says the same thing.

    The article says

    “The pool has as many threads as os.availableParallelism(), up to 8 by default, or as many as the NODE_GREEN_THREADS_POOL_SIZE environment variable sets”

    The source says

    “The pool has as many threads as [`os.availableParallelism()`][], up to 8, or as many as the [`NODE_GREEN_THREADS_POOL_SIZE`][] environment variable sets”

    Source cited by the article: github.com/jasnell/node/blob/green-threads/doc/api/green_threads.md

  4. No source givenNumber

    A green thread uses about 4.5x less memory than a worker (1.4 MB vs 6.2 MB per instance).

    The article gives no link or citation for it.

    The article says

    “A green thread uses about 4.5x less memory than a worker”

    The source says

    No source to compare with.

  5. No source givenNumber

    Starting green threads from a warm pool reaches about 83,000 per second, versus about 950 per second for workers.

    The article gives no link or citation for it.

    The article says

    “Green thread, from a warm pool 1.4 MB ~83,000”

    The source says

    No source to compare with.

  6. No source givenBenchmark result

    In a 1,000-tenant benchmark, a green thread per tenant served about 195,000 requests per second versus about 160,000 for a worker per tenant.

    The article gives no link or citation for it.

    The article says

    “A green thread per tenant ~195,000”

    The source says

    No source to compare with.

  7. No source givenBenchmark result

    Without a timeout, green threads and a vm pool have the same throughput, but with timeout: 50 the vm pool serves less than half as many requests.

    The article gives no link or citation for it.

    The article says

    “Without a timeout, throughput is the same, and the vm pool has better tail latency”

    The source says

    No source to compare with.

  8. No source givenGeneralization

    At the same parallelism, green threads run CPU-bound code at about the same speed as workers, and they cannot use more cores than the pool has threads.

    The article gives no link or citation for it.

    The article says

    “At the same parallelism, the same code runs at about the same speed. Green threads don't make computation faster”

    The source says

    No source to compare with.

Also covered by

No other coverage was clustered with this story.

Elsewhere

Elsewhere: HN 2 pts, not on front page

Discussion on Hacker News

Recorded for context only, checked 18 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 “Green Threads for Node.js”

More on Rubric

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