Re: [streams] New proposal for byte stream uses cases (#289)

I have been investigating an idea similar to yours. That's exposing WritableStream (stream for feeding) and ReadableStream (output emitter) on the ReadableByteStream. Your `wait(current)` resembles `write(value)` of the WritableStream. You've hidden weirdness of calling `write()` for non-byte-stream by naming it `wait()` and made its argument optional. This looks good point but I'm still not sure. There could be some pitfall.

read() has the same signature as ReadableStream (object stream), but how piping between object stream and byte stream would be like? I think we should list what we mean by "compatibility with object stream" concretely and prototype how it'll be like. Does `wait()` call required for each read() even for object stream or it'll be just like the old ReadableStream where it's just a kicking switch of pulling.

Just a naming preference, but I prefer `pull()` to `wait()`.

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