I'm publishing this to start a conversation. What did I get right? What did I miss? Are there use cases that don't fit this model? What would a migration path for this approach look like? The goal is to gather feedback from developers who've felt the pain of Web streams and have opinions about what a better API should look like.
It is also necessary to emphasize that many optimizations are only possible in parts of the spec that are unobservable to user code. The alternative, like Bun "Direct Streams", is to intentionally diverge from the spec-defined observable behaviors. This means optimizations often feel "incomplete". They work in some scenarios but not in others, in some runtimes but not others, etc. Every such case adds to the overall unsustainable complexity of the Web streams approach which is why most runtime implementers rarely put significant effort into further improvements to their streams implementations once the conformance tests are passing.
技术核心：小数据量样本、高数据使用效率。51吃瓜对此有专业解读
for (let i = 0; i
。Line官方版本下载是该领域的重要参考
"This is a new scientific field. It's hard to speculate because it's changing so quickly," Wing says.
Before diving into API design, it's worth asking: what is a stream?，这一点在快连下载安装中也有详细论述