Re: [streams] Merge ReadableByteStream into ReadableStream (#430)

Yeah, I get that. Maybe we should just merge everything into one blob, but I liked the idea of reusable queuing strategies that could be constructed independently. E.g. you could imagine client code writing

```js
const qs = new CountQueuingStrategy(12);
someLibrary.getMeAStream(qs);
```

and then it just forwards the object along to the stream implementation.

That is, the main separation is that underlyingSource contains properties relevant to the stream creator, whereas queuingStrategy is something the consumer might be interested in setting.

WDYT?

---
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/streams/pull/430#issuecomment-195126525