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

>From my perspective as a Chrome implementer, adding a TextEncoderTransformStream object means duplicating a bunch of TextEncoder code. The extra bindings generated from the IDL file will have a non-trivial cost in binary size. Every extra symbol we add to the global object incurs a cost in time and memory for every iframe created.

Looking at it as a consumer of the API, we just made them remember whether it is TextEncoderTransformStream or TextEncoderStream or TextEncoderTransform or TextStreamEncoder or TextTransformEncoder or something else, and type an extra 15 characters, for no benefit to them whatsoever.

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

Received on Friday, 23 March 2018 11:21:14 UTC