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.
Watch: Astronauts return to Earth after extended stay in Space
，这一点在WPS官方版本下载中也有详细论述
"Other people in the street, they have kids, grandkids, so it's a lot more difficult for them."
第五十三条 有下列行为之一的，处五日以下拘留或者警告；情节较重的，处五日以上十日以下拘留，可以并处一千元以下罚款：