The problem gets worse in pipelines. When you chain multiple transforms — say, parse, transform, then serialize — each TransformStream has its own internal readable and writable buffers. If implementers follow the spec strictly, data cascades through these buffers in a push-oriented fashion: the source pushes to transform A, which pushes to transform B, which pushes to transform C, each accumulating data in intermediate buffers before the final consumer has even started pulling. With three transforms, you can have six internal buffers filling up simultaneously.
18 February 2026ShareSave
。搜狗输入法2026对此有专业解读
17:38, 27 февраля 2026Силовые структуры
2026-02-28 00:00:00:0本报记者 祝佳祺 韦军委员——
There's also Stream.broadcast() for push-based multi-consumer scenarios. Both require you to think about what happens when consumers run at different speeds, because that's a real concern that shouldn't be hidden.