Randell Jesup

random UUIDs could help avoid accidental exposure of info, and as mentioned avoid accidental dependence on a particular hashing format by developers using this. Does this buy any advantage to...

The ability to get the Parent of an item is a common FileSystem API point

The comments you point to discuss a number of issues that don't apply to OPFS (since you don't get handles from a picker); we always know and can easily return...

Good. It really never made sense to me that the API specifically to provide sync access was (mostly) async. So... why can't createSyncAccessHandle (aka open()) be sync? This would require...

Since making FileSystemSyncAccessHandles fully sync is something of a breaking change, how should we go about it? While a few apps are using this API already (Photoshop), they're still in...

Correct, only one thread can access a SyncAccessHandle. Having them be more similar to WritableFileStream and (not in the spec) AccessHandle has some benefit, but as mentioned (and mentioned in...

if async operations can queue, then read/write would need to remain sync, which means all async operations would need to finish/resolve before the read/write occurs and returns. If one of...

If the issue with WASM that requires synchronous APIs is that a Promise resolution/await involves a microtask, and the long-term solution is https://github.com/webAssembly/js-promise-integration, then why is it ok to have...

See also issue #7 If there are reasons we can't use async APIs here (for WASM), why do have a mix? Why not make them all sync? (and I'd probably...

So "snapshot state" ("Set f’s [snapshot state](https://w3c.github.io/FileAPI/#snapshot-state) to the current state of entry.") indicates that the data returned may not reflect later changes to the file; implying a read-into-memory (or...