Re: [streams] listen() (#341)

@domenic on my current use case (2-way communication between worker/window) I need the basic features of the Readable/Writable streams (`cancel`, `abort`, `write`, `close`, `closed`), but it's really closer to an *observable* since I expect the window to be able to handle all the data that is sent by the worker without needing to *pull* it (I expect the consumer to buffer/queue it by themselves if needed). I'm using the streams spec as a reference for my API/features but I ended up adding the `listen()` method to the *readable stream* itself just to keep things simple. We currently don't need the sink/pipe/buffering/pull logic.

I'm trying to avoid the need for *yet-another-helper-lib* (eg. `jQuery` for Streams), but I totally understand if that is not a *"programming style we want to encourage"*.

---
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/streams/issues/341#issuecomment-95236491