7 ms·

Are you sure you're up to date on the latest additions to this API? This wasn't in the MVP: > The origin private file system provides optional access to a spec

Are you sure you're up to date on the latest additions to this API? This wasn't in the MVP: > The origin private file system provides optional access to a special kind of file that is highly optimized for performance, for example, by offering in-place and exclusive write access to a file's content. https://web.dev/file-system-access/#accessing-files-optimized-for-performance-from-the-origin-private-file-system https://web.dev/file-system-access/#accessing-files-optimize... It was originally going to be a separate high-perf "Storage Foundation" API, but that was merged with the File System Access API.

chrismorgan 4y ago
Huh. Disregard what I wrote entirely, then. Reading through https://github.com/WICG/file-system-access/blob/main/AccessHandle.md https://github.com/WICG/file-system-access/blob/main/AccessH..., I can see how they’ve bypassed most or all of the problems I saw—I was making unnecessary assumptions. Thank you for correcting me. I am now enthusiastic about OPFS.
- ankoh 4y ago
  This has to be ruled out first: https://github.com/whatwg/fs/issues/7#issuecomment-1161768515 https://github.com/whatwg/fs/issues/7#issuecomment-116176851... ...but then the OPFS will be a quite decent fit. We (DuckDB-Wasm) are also looking closely at OPFS. IMHO the requirement here is not even to get to full ACID. With OPFS, we will get close enough to IndexedDB on steroids and bypassing the js heap limits through out-of-core operators. After all, we are still running in a browser. So I see the value of Wasm-based databases to be a front-facing accelerator, not a substitute for robust storage solutions.
- SomaticPirate 4y ago
  Great to see this kind of pleasant discourse on HN!