![]() Amazing for a forever-running browser/runtime that never crashes, but pointless as persistent DB sql.js is not persistent: it runs SQLite on RAM, it stores the DB on RAM too, but then it vanishes on each refresh. ![]() legacy browsers won’t work (but personally I wouldn’t care for PWAs, as legacy browsers don’t run PWAs neither).What are we missing then? Why are not all on board? So, there is this sql.js project, which brings SQLite to the Web, and there is IndexedDB, which can store the buffer exported by sql.js. ![]() The community, myself included, has never been too happy about the choice W3C made, and while reasons for dropping WebSQL made sense, nothing ever filled that gap … until recent days, where C or C++ programs could target WASM, and WASM could run everywhere, most importantly, on the Web.
0 Comments
Leave a Reply. |