February 27, 2026
Streams? More like screams
We deserve a better streams API for JavaScript
Dev world erupts: fix streams now or ditch JavaScript
TLDR: A prominent dev says the web’s streaming tool is outdated and shows a new approach that can be up to 120x faster. Comments explode: performance fans want easier memory control, skeptics say ditch JavaScript, and others cry “LLM vibes,” all agreeing it’s time to make streaming fast and simple.
A veteran runtime engineer just threw a firecracker into web dev world: the browser’s official streams system — the way apps move data piece by piece — is outdated, clunky, and slow. His pitch? A simpler design using modern JavaScript that he says runs 2x to 120x faster across browsers and servers, powering things like fetch() and more. He insists he’s not trashing the old guard, just pushing for a reboot of the Web Streams standard born in 2014–2016, before today’s nicer “for await” tools existed.
The comments? Absolute chaos. Performance diehards are laser-focused on BYOB — “bring your own buffer,” a memory-saving trick — raging that it’s so hard to use that devs give up and burn CPU instead. One commenter basically says “just use raw internet pipes,” another accuses the author of giving off “LLM” (AI ghostwriter) vibes, and a third drops the nuclear option: “We deserve a better language than JavaScript,” with a side-eye that “WebAssembly didn’t save us.” The meme energy is strong: “streams vs screams,” “Bring Your Own Burnout,” and “async all the way down.” Underneath the jokes, a rare consensus forms — locks, readers, and boilerplate feel like museum pieces next to today’s simpler patterns, and everyone wants speed without the headache.
Key Points
- •The WHATWG Streams Standard unified streaming APIs across browsers and server runtimes and underpins fetch().
- •The article argues Web streams have fundamental usability and performance issues tied to early design decisions.
- •An alternative approach using modern JavaScript primitives is proposed, claiming 2x–120x faster benchmarks across major runtimes.
- •The Streams Standard predates async iteration (for await...of), leading to a reader/writer lock model and added complexity.
- •Node.js had its own streaming API, but WHATWG focused on browser needs; server-side adoption of Web streams came later for cross-runtime compatibility.