I found this article on the subject, and decided to turn that data into a visualization, too.
You might assume this pattern is inherent to streaming. It isn't. The reader acquisition, the lock management, and the { value, done } protocol are all just design choices, not requirements. They are artifacts of how and when the Web streams spec was written. Async iteration exists precisely to handle sequences that arrive over time, but async iteration did not yet exist when the streams specification was written. The complexity here is pure API overhead, not fundamental necessity.
，详情可参考Line官方版本下载
What this means for the web
From this moment, Scream 7 doesn't just wink at the long-time Scream fans, who are greedily eying every frame for Easter eggs. It waves at us with a fervent reminder that knowing about these movies doesn't mean you'd survive them. (RIP Randy, the first to teach us this lesson.)