3 ms·

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

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.

Beltalowda 4y ago
> Sqlite updates are solid and as far as I know, do not break your code. 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.
- modeless 4y ago
  Browser engines have regressions too. SQLite has a better test suite than any browser. It's not going to be a major source of regressions compared to the rest of the platform.
  - hochmartinez 4y ago
    That's correct. SQLite has an impressive test suite that makes it very stable. That's why it's used in millions of Android devices or will be used in Cloudflare's edge with D1, for example.
    - sgbeal 4y ago
      > That's why it's used in millions of Android devices 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).
josephg 4y ago
The downside of that is that application developers would have to use the minimum supported version of SQLite. 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)
- hochmartinez 4y ago
  We have the same problem with the library in the OS. And with the default compilation, SQLite usually works fine.
- ilyt 4y ago
  > The downside of that is that application developers would have to use the minimum supported version of SQLite. 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
kevingadd 4y ago
This would provide more ways to fingerprint users. It's also not possible to guarantee no sqlite update will ever change observable behavior, even if it happens to mostly be true now. 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.
- ilyt 4y ago
  > This would provide more ways to fingerprint users. It's also not possible to guarantee no sqlite update will ever change observable behavior, even if it happens to mostly be true now. Browser behaviour changes (and even breaks) way often than SQLite does.
sgbeal 4y ago
> Sqlite updates are solid and as far as I know, do not break your code. 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 https://sqlite.org/wasm/doc/trunk/api-index.md>

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.

Beltalowda 4y ago

> Sqlite updates are solid and as far as I know, do not break your code. 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.

modeless 4y ago
Browser engines have regressions too. SQLite has a better test suite than any browser. It's not going to be a major source of regressions compared to the rest of the platform.
- hochmartinez 4y ago
  That's correct. SQLite has an impressive test suite that makes it very stable. That's why it's used in millions of Android devices or will be used in Cloudflare's edge with D1, for example.
  - sgbeal 4y ago
    > That's why it's used in millions of Android devices 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).

josephg 4y ago

The downside of that is that application developers would have to use the minimum supported version of SQLite. 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)

hochmartinez 4y ago
We have the same problem with the library in the OS. And with the default compilation, SQLite usually works fine.
ilyt 4y ago
> The downside of that is that application developers would have to use the minimum supported version of SQLite. 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

kevingadd 4y ago

This would provide more ways to fingerprint users. It's also not possible to guarantee no sqlite update will ever change observable behavior, even if it happens to mostly be true now. 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.

ilyt 4y ago
> This would provide more ways to fingerprint users. It's also not possible to guarantee no sqlite update will ever change observable behavior, even if it happens to mostly be true now. Browser behaviour changes (and even breaks) way often than SQLite does.

sgbeal 4y ago

> Sqlite updates are solid and as far as I know, do not break your code. 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 https://sqlite.org/wasm/doc/trunk/api-index.md>