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.
小马拉大车的结果显而易见：高喊着取代 iPhone 的 Ai Pin 续航崩盘、发热烫人，最终随着服务停止、公司出售，产品也沦为昂贵且无用的电子垃圾。，这一点在heLLoword翻译官方下载中也有详细论述
Paul Copplestone Co-founder & CEO, Supabase，更多细节参见搜狗输入法2026
Date: February 24, 2026
self.config.sleep_max