Re: [whatwg/encoding] Add support for whatwg streams (9224c4c)

@jakearchibald That's an interesting alternative. ```stream.pipeThrough(new TextEncoder())``` is a very attractive interface.

I have two concerns I'd like more feedback on:

1. Spec complexity. The encoding spec would end up with quite a lot of text basically copy-and-pasted from the definition of TransformStream in the streams spec. Maybe this could be mitigated by "exporting" the necessary methods from the streams spec so that they could be reused in the encoding spec?
1. Implementation optimisation cost. I expect implementations will want to optimise TransformStream to bypass the cost of flow-control tracking and buffer-juggling where possible. But if TextEncoder doesn't use TransformStream directly, then it could easily fall through the cracks or require duplicate optimisation effort.

-- 
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/commit/9224c4cad81fd5720306fe79241cf04b5526a3f0#commitcomment-19169733

Received on Monday, 26 September 2016 09:40:57 UTC