Re: [w3ctag/design-reviews] TextEncoderStream and TextDecoderStream (#282)

Hey Adam,

Thanks for filing for a review, and apologies for the delay in getting back to you.

Some questions regarding the merged PR:

 * Why are [UTF-8, UTF-16BE, and UTF-16LE treated differently to other encodings (in a hard-coded way) regarding BOM treatement?](https://encoding.spec.whatwg.org/#interface-mixin-textdecodercommon)
 * The [`GenericTransformStream`](https://encoding.spec.whatwg.org/#interface-mixin-generictransformstream) mixin creates `readable` and `writeable` properties, but it doesn't appears as though internal aspects of these default streams are configurable. That is, the [various flags one can pass to Stream constructors](https://streams.spec.whatwg.org/#rs-constructor) aren't available for configuration when instantiating one of these stream types. This makes certain built-in stream types "magically" faster and perhaps more flexible than userland stream types, violating layering expectations. Perhaps there's a way to configure them that I've just missed?
 * I'm not able to locate much in the way of example code outside of the [`encoding/streams/` WPT tests](https://wpt.fyi/results/encoding/streams?aligned&label=stable). There [isn't a ton in the Explainer either](https://github.com/ricea/encoding-streams/blob/master/stream-explainer.md). It'd be helpful to see examples that show problems being solved rather than just "how to use it here".
 * The Explainer states that it's a non-goal to provide encodings other than `UTF-8`. Is it possible to create your own subtype to handle other encodings? If not, why not?

Regards

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3ctag/design-reviews/issues/282#issuecomment-434313834