This is the intuition the new API tries to preserve: streams should feel like iteration, because that's what they are. The complexity of Web streams — readers, writers, controllers, locks, queuing strategies — obscures this fundamental simplicity. A better API should make the simple case simple and only add complexity where it's genuinely needed.
虽然冠以AI便自带了智能交互的噱头，但要想建立护城河，给音箱套个毛绒外壳显然不够，还是需要真正提升交互体验，或者说，提供独特的陪伴感。一方面，通过技术创新，从通用型走向个性化；另一方面则是利用IP的打造，与使用者之间建立起情感连接。
，这一点在同城约会中也有详细论述
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.
现在，比任何时候我都更怀念史蒂夫那种独特而清澈的清晰感。超越想法与愿景本身，我怀念的是他那种能够为混乱建立秩序的洞见。
// console.log(dailyTemperatures([30,40,50,60])); // [1,1,1,0]