Benjamin Gruenbaum

Benchmark CI: https://ci.nodejs.org/view/Node.js%20benchmark/job/benchmark-node-micro-benchmarks/1561/

Benchmarks look great: ``` 10:03:02 confidence improvement accuracy (*) (**) (***) 10:03:02 worker/atomics-wait.js n=10000000 0.05 % ±0.59% ±0.79% ±1.03% 10:03:02 worker/bench-eventlooputil.js method='ELU_passed' n=1000000 0.64 % ±0.67% ±0.90% ±1.18% 10:03:02 worker/bench-eventlooputil.js...

Fwiw the plan for what became `worker_threads` initially in 2015 was to eventually replace cluster's internals with worker_threads. Petka did early experiments that showed promise. > For 1... it is...

> It does not, us doc-deprecating it does not mean folks can not use it, only that our documentation recommends against doing it. So the plan is to doc deprecate...

Then I am -1 on this unless it is clear we don't runtime deprecate and make it harder to write universal code

> Would you mind elaborating why it makes it harder to write universal code? Users would use libraries that work in Node.js and browsers, those libraries would start emitting a...

> If a library tries to pass a NaN I would take a wild guess that it was most likely a mistake probably should be patched As a platform, changing...

> Why is it important to you that the warning is not a deprecation? How would it be different from a deprecation? I am opposed to changes or signals that...

> IIUC, this sentence is not what you believe, but rather what you believe the users (or at least non-negligible portion of Node.js users) will interpret the deprecation, correct? Do...

I feel like I'm blocking this needlessly and causing frustration which I hate doing (since making progress is hard as is) and we should discuss this further or in the...