its interesting, but it is not robust and I very much doubt it will have the claimed benefit for lasting without further work. At the very least its more work and requires cross browser testing.
It seems a lot of effort just to avoid paying a small amount a month for a VPS. Its free and " I forget about the backend and stop paying for whatever VPS it was on" stops being a problem (although running all the little things you have on one VPS would also simplify that).
[1] - https://mrtimo.github.io/spokane-co-biz/#/model/businesses/e... [2] - https://github.com/aszenz/data-explorer
>> phiresky/sql.js-httpvfs: https://github.com/phiresky/sql.js-httpvfs
>> mmomtchev/sqlite-wasm-http: https://github.com/mmomtchev/sqlite-wasm-http
>> This project is inspired from @phiresky/sql.js-httpvfs but uses the new official SQLite WASM distribution
duckdb/duckdb-wasm: https://github.com/duckdb/duckdb-wasm
electric-sql/electric: https://github.com/electric-sql/electric :
> Specifically, Electric is a read-path sync engine for Postgres. It syncs data out of Postgres into ... anything you like. The core sync protocol is based on a low-level HTTP API. This integrates with CDNs for highly-scalable data delivery.
electric-sql/pglite: https://github.com/electric-sql/pglite :
> Embeddable Postgres with real-time, reactive bindings.
"Using Postgres for Everything" https://news.ycombinator.com/item?id=40420474
>(or IPFS or any static file hoster)