Re: [filesystem-api] Observable is not appropriate for directory listing; async iterable would be better (#4)

We did a pretty hefty real-world performance comparison for this sort of stuff in streams and found that the cost of promise allocations was absolutely trivial. The actual I/O is where all the work happens.

The motivation for backpressure here is quite simply to avoid the extra I/O---which is where the real cost lies.

---
Reply to this email directly or view it on GitHub:
https://github.com/w3c/filesystem-api/issues/4#issuecomment-106983517