[mg]

    While in-memory databases have their uses, it kneecaps
    SQLite into something far less useful. To build any
    kind of app with it, we need the ability to write and
    persist.

Another approach than writing the data to a server could be to allow the user to store it on their own hard disk.

This could be done via the File System Access API:

https://developer.mozilla.org/en-US/docs/Web/API/File_System...

The API already works nicely in Desktop Chrome:

https://googlechromelabs.github.io/text-editor/

[jlongster]

Did you read the post? This project does exactly that. (but focuses in IndexedDB for now because it's the only cross-browser thing that works. I actually tried a webkitFileSystem backend and it was slower)

[mg]

Well, I woudln't call using IndexedDB "exactly that". As IndexedDB is rather fleeting. You don't use a server, that is correct. But IndexedDB goes away under many circumstances. Saving a file via the File System Access API would give the user peace of mind that it is safe. I did not see any mention of the File System Access API in your post.