Re: [whatwg/streams] Allow web devs to synchronize branches with tee()? (#1157)

> Maybe the problem is tee() and not streams?

This would break point 3 of where readable stream fits best, according https://github.com/whatwg/streams/blob/main/FAQ.md:
```
Readable streams fit best in situations where:
1. You are trying to represent some underlying I/O source of data, especially one for which backpressure is meaningful.
2. Consumers care about the logical concatenation of all chunks of the stream, such that every value produced is important.
3. Your usual use case is a single consumer, with allowances for multi-consumer via teeing.
4. Errors are either final and non-recoverable (socket prematurely closed), or just a specialized type of data (404).
```

Points 2 and 3 are not met in the context of a realtime video processing pipeline.
Point 4 is also debatable: errors are not a type of data and errors are generally recoverable in a video processing pipeline.

-- 
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/streams/issues/1157#issuecomment-895847764