Adam Rice

There was some discussion of SAB with streams previously here: https://github.com/whatwg/streams/issues/495#issuecomment-284083329 It seems likely that we will add a way to use a SAB without transferring. Unfortunately it doesn't look...

I think this is useful as a separate issue. I've marked it with Milestone V2 to reflect that it's not something we'll be changing immediately.

If in future we'd like TextEncoderStream's `readable` side to be a byte stream then we have a conflict here. It's undesirable for user code to be able to view the...

I don't think we're likely to add callback-based APIs. Eliminating the promise from the external API wouldn't eliminate the promise returned from pull(), nor the other objects that are created...

Currently the way you'd do this is by having the Zlib transform decide for itself to flush based on a timeout. This is obviously not good as the transform has...

Server-side use cases are still important. I don't want a permanent fork of the standard on the server-side, but maybe a temporary addition to the API to explore how well...

Related: https://github.com/ricea/compressstream-explainer/issues/3.

This is useful for WebCodecs: https://github.com/WICG/web-codecs/blob/master/explainer.md. So I'm considering increasing the priority of this request. In addition to passing a sync down a pipe from the source, it might also...

Bikeshedding in moderation is welcome :smile_cat: My current position is that the use cases are sufficiently compelling to add `sync()` methods to ReadableStream and TransformStream controllers, underlying transformers and sinks,...

The issue is not urgent (at least for Blink), so we can take the time to do it properly.