Re: [whatwg/encoding] Add Streams support (#72)

Sorry for bringing up the inheritance of implementation thing. That's a much wider issue that should be discussed elsewhere.

I've discussed this extensively with @domenic and we see TransformStream as a convenience factory for a `{ readable, writable }` "structural object" to be consumed by `pipeThrough()`. It provides the nice properties that most people would want, but it's not the _only_ way to get a `{ readable, writable }` pair. https://streams.spec.whatwg.org/#example-both is an example of another way. TextEncoderStream would be another of those other ways.

We're not looking to extend TransformStream to have extra attributes beyond `readable` and `writable` because it would be preferable to find ways to make every `{ readable, writable }` pair more functional instead.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/encoding/issues/72#issuecomment-396882904