sqlite3.wasm should be included in Chrome, Firefox, Safary, Brave, etc. And updated automatically.
Sqlite updates are solid and as far as I know, do not break your code.
Sqlite updates are solid and as far as I know, do not break your code.
If every site embeds their own version, the application developers can choose their own version that runs the same across every browser. Or even compile it themselves if they want, so they can use extensions. The download size is unfortunate but remember - unlike javascript, wasm bytecode loads almost instantly. Having a 250k wasm module is more like having a 250k image on your site than 250k of javascript. (Though it might still affect time-to-interactive depending on how the site is built)
Nope. The downside is that some applications that want to use new one would have to download it, and the remaining 90% could use builtin one
Almost every major SQLite release has a few minor releases after it which fix bug and regressions, including things like queries returning the wrong result.
s/millions/billions/g. It is widely believed to be either the single most widely-deployed piece of software in the world, or maybe second behind zlib (we have no way of being sure).
Once you start giving special privileges to specific wasm binaries, the floodgates are open for a hundred different vendors to demand the same special treatment because 10% of websites use their .wasm blob. And then you've created a barrier to entry for competition. Nobody wins in the long run except a couple of your friends.
Browser behaviour changes (and even breaks) way often than SQLite does.
That applies to the C code. The wasm code is still in beta, and won't see a public beta release until 3.40 is released in November. See the notes about API stability here: <https://sqlite.org/wasm/doc/trunk/api-index.md>