4 ms·
> It has to be downloaded and JIT compiled separately for every site that uses it I don't really see the problem with that. Looking at the sql.js demo[1] the W
by Beltalowda 4y ago
> It has to be downloaded and JIT compiled separately for every site that uses it
I don't really see the problem with that. Looking at the sql.js demo[1] the WASM binary is 610K (305K compressed/transferred), and it seems to run pretty fast even on my slow laptop.
> Maybe if half the sites on the web start using it
Most websites have no reason to use it; simple key/value localStorage is enough for many sites or apps that need some sort of storage. It's kind of a niche thing. Many regular desktop applications have no need SQLite, either.
- wruza 4y agoIt’s an ubiquitous need for any app that has a dynamic collection view. You can’t take all sites, see that 99% of them are static documents developed as degenerate apps and then conclude that “most apps” have no reason to use it. It’s like saying that most cats are on jpegs, so cat food is kind of a niche thing for a cat owner.
- Beltalowda 4y ago> “most apps” Please do not put words in quotes as if I said them when, in fact, I did not. Thank you.
- wruza 4y agoWhat would that trivial correction change, in your opinion?
- ilyt 4y ago> I don't really see the problem with that. Looking at the sql.js demo[1] the WASM binary is 610K (305K compressed/transferred), and it seems to run pretty fast even on my slow laptop. ...and that is small by your standards ?
- Beltalowda 4y agoIt's not small; it's also not huge. For the type of website that has use for this it's not really all that much.
- sgbeal 4y ago> Most websites have no reason to use it; simple key/value localStorage is enough for many sites or apps that need some sort of storage. In case you hadn't noticed it, the new sqlite features include using localStorage and sessionStorage as db backend storage :). <https://sqlite.org/wasm/doc/trunk/persistence.md#kvvfs https://sqlite.org/wasm/doc/trunk/persistence.md#kvvfs>