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

> The main problem with the first option as I see is that stream() ends up creating an object there's no way to create through a constructor. And while we have some of that in the platform, the preference from the developer community is that we avoid such magical creation patterns.

There is a way to create it: it directly uses the TransformStream constructor. There's no magic going on here, just an algorithm for assembling the constructor arguments.

In general I think a clean break between the stream interface and the old interface would be preferable, instead of a confusing mismash which has both APIs on the same object, and which raises questions about what happens when you mix them. (Answerable questions, but the answers are not necessarily intuitive.)

-- 
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-251408394