Does this have any relation to: https://github.com/vlcn-io/cr-sqlite ?

Some of the API naming is similar (db_version, site_id, seq, commit_alter, etc), although the project source is very different (C rather than Rust, different feature set).

crsqlite is no longer maintained so I might be interested in migrating.

API naming looks similar, probably because we are based on the same scientific paper: https://munin.uit.no/bitstream/handle/10037/24430/article.pd...

I am fully on the offline-first bandwagon after starting to use cr-sqlite (https://vlcn.io), which works similar to ElectricSQL.

I thought the bundle size of wasm-sqlite would be prohibitive, but it's surprisingly quick to download and boot. Reducing network reliance solves so many problems and corner-cases in my web app. Having access to local data makes everything very snappy too - the user experience is much better. Even if the user's offline data is wiped by the browser (offline storage limits are a bit of a minefield), it is straightforward to get all synced changes back from the server.

Yeah, 1mb of WASM != 1mb of JS.

WASM is much faster to start up since you don't have all the parsing and compiling overhead.

Yes, I have trialled this. I've found it works best with this workflow:

  1. Summarise some prose (from a textbook) into bullet points
  2. Convert these to flashcards
  3. Make these flashcards more concise

I then verify they are correct/relevant, only keeping those that are worthwhile.

Hosted PostgreSQL service with exposed HTTP API and ACL/validation hooks. Also syncing hooks to plug into SQLite/iDB/etc for offline apps.

Sort of like Cloudant/Firebase but using relational db.

Not quite what you are suggesting but....

http://aws.amazon.com/rds/postgresql/