This is better in that there is far less boilerplate, but it doesn't solve everything. Async iteration was retrofitted onto an API that wasn't designed for it, and it shows. Features like BYOB (bring your own buffer) reads aren't accessible through iteration. The underlying complexity of readers, locks, and controllers are still there, just hidden. When something does go wrong, or when additional features of the API are needed, developers find themselves back in the weeds of the original API, trying to understand why their stream is "locked" or why releaseLock() didn't do what they expected or hunting down bottlenecks in code they don't control.
To what extent developer activity is tracked across the ecosystem
，这一点在夫子中也有详细论述
You immediately must scale “the wall” of wrangling the many different pieces to work together. The end result is often only worth it for large projects.。关于这个话题，旺商聊官方下载提供了深入分析
FT Videos & Podcasts