Many programming languages have some kind of representation of a stream, a sequence of bytes (or objects) that can be processed a chunk at a time, filtered, transformed, composed, pipelined, split, merged and so on. JavaScript is no exception, but historical peculiarities of the language have left it in kind of a bad place for the ergonomics of using streams. So this article discusses improvements that could be made. PL students take note: we’ve moved on from mere syntax and semantics to the squishy yet ultimately valuable worlds of ergonomics and pragmatics!