# Node.js worker_threads

6 Hacker News commenters recommended Node.js worker_threads and 5 criticized it, November 2025 to November 2026. It was recommended in 3 of 13 months.

**Verdict:** Recommended for running JavaScript work in parallel threads with message passing and easy bolt-on use. Most common caveat is awkward ergonomics and costly data serialization between threads.

## What people warn about

- Awkward ergonomics and complicated API (2 comments): "The friction mainly comes from ergonomics, as pointed out in the article." ([source](https://news.ycombinator.com/item?id=47480023)) "the api is kind of low-yet-high-level and that brings some complications" ([source](https://news.ycombinator.com/item?id=47480187))
- Serialization cost and weak backpressure (2 comments): "The lack of backpressure handling nor promise api for postMessage is also quite annoying, I had many OOMs because of it." ([source](https://news.ycombinator.com/item?id=47478425)) "The serialization cost of passing data between threads ate most of my gains" ([source](https://news.ycombinator.com/item?id=47477104))

## Alternatives hackers recommend

- [Tokio](https://hackerapproved.com/p/tokio.md): 57 recommend
- [Akka](https://hackerapproved.com/p/akka.md): 12 recommend
- [ZIO](https://hackerapproved.com/p/zio.md): 11 recommend
- [Trio Python library](https://hackerapproved.com/p/trio.md): 10 recommend
- [core.async](https://hackerapproved.com/p/core-async.md): 9 recommend

## Cite as

Hacker Approved, "Node.js worker_threads", https://hackerapproved.com/p/node-js-worker-threads/ (counts from 1,795,640 Hacker News comments, November 2025 to November 2026).