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

@wycats I don't really find reasoning from constraints that compelling in this case. Rather, I'd prefer a primitive that maps directly to the underlying OS operations, thus allowing maximum flexibility. You could even imagine an awkward API that does a direct translation (using some kind of "directory handle" JS object). That IMO would be better than any proposal that tries to fire events at you continuously. It's a nice fact that async iterator maps to the OS operations directly.

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