WebContainer, file system APIs & sqlite #19
Replies: 2 comments 5 replies
-
It is the FS Access API since www.StackBlitz.com/local throws |
Beta Was this translation helpful? Give feedback.
-
I got excited enough to look at the File System Access API when support recently showed up in Safari, but unfortunately it doesn't look good for storing live databases. Besides the fact that Firefox is opposing it, the Chromium implementation appears to be crippling performance in the name of security. According to this bug, writing to a file copies the file, applies the write to the copy, scans the copy for malware, and renames the copy over the original. If you're updating a small area of a large file, e.g. like a database transaction, and your local filesystem doesn't do some sort of block deduplication, then that could be excruciatingly slow. So far the Google response seems to be, "works as intended". |
Beta Was this translation helpful? Give feedback.
-
It seems like a bunch of stuff was released for Google I/O ;) Something that caught my attention:
WebContainer OSS repo (docs only): https://github.com/stackblitz/webcontainer-core
HN thread: https://news.ycombinator.com/item?id=27223012
Blog post: https://blog.stackblitz.com/posts/introducing-webcontainers/
Comment mentioning sqlite: https://news.ycombinator.com/item?id=27224683
I’m curious about WebContainers appearing out of the blue, what exact file system API is being used (File System Access API?) and whether threads are involved in their sqlite adaption. As always, I’m hoping a proper FS API and WASM threads become available cross-browser.
Beta Was this translation helpful? Give feedback.
All reactions