这是将对代表的政治要求熔铸于人民代表大会制度设计之中的深刻考量。
And I remember at one point I made a analogy with gun laws or gun regulation or something.
，这一点在heLLoword翻译官方下载中也有详细论述
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.
That’s the cornerstone of Modular Design and that’s why it was already mentioned several times in this article. It’s about “hiding in a box” how something is implemented without requiring other developers, who just use your module, to know any of the inner workings. It hides inner complexity. That implies that the public API of the module is on the higher level of abstraction (agnostic of the details). That’s desirable because it lowers the cognitive load on the users (they don’t have to be experts in whatever the module is doing as long as the public API is easy). Another benefit is that it allows you to change the implementation without breaking other modules.