We deserve a better streams API for JavaScript

This blog post critiques the design and practical shortcomings of the Web Streams Standard—calling out excessive ceremony (readers/locks), BYOB complexity, weak backpressure guarantees, promise-heavy hot paths, tee() memory cliffs, and GC pressure in streaming SSR—and presents a proof-of-concept alternative API built on async iterables that emphasizes pull-based transforms, batched byte chunks, explicit backpressure policies, synchronous fast paths, and clear multi-consumer semantics; the author supplies benchmarks showing large throughput gains and a reference implementation to spark community discussion.