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

I don't think so, at least, not the types of optimizations we're thinking of for Chrome. For example, you can use the specialized knowledge that TextEncoderStream is synchronous to do optimizations far beyond what you could do on any generic TransformStream.

The optimizations you could do on a generic TransformStream are pretty limited, in fact, given that generically speaking, TransformStream instances call out to user JavaScript code all the time. So optimizations will generally be done on specific, recognized, branded pairs of { readable, writable }. That could even include a WebSocketDuplexStream in the style of #example-both if we ever got around to adding that to the platform.

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