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

Sorry for the long silence. I have been trying to figure out how to resolve the deadlock.

It seems there are no disagreements regarding facts, only about priorities. There also isn't an unambiguous majority in favour of any option. Reaching consensus is going to be hard as long as people have differing priorities. I would like to ask @annevk, as the editor, to decide the direction.

I think we have three options left on the table:

1. `pipeThrough(new TextDecoder())`, with distinct state.
2. `pipeThrough(TextDecoder.stream())` returning a TextDecoderStream object, without a constructor on the global object.
3. `pipeThrough(new TextDecoderStream())`.

There's something we've not yet discussed about the third option: are `TextDecoderStream` and `TextEncoderStream` going to inherit from `TransformStream`? I have a strong preference for the answer to be "no", as I expect that having a WebIDL-defined object inherit from a Javascript-defined object would create difficulties for both the standard text and implementations.

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